Very high cpu usage

[rakesh-roshan]

I did the load testing for rulio service with around 200 concurrent connections. The machine is 2 core 2.66 GHz and 8 GB RAM. With just 200 concurrent requests, the CPU Load touches 100%. The average rate is 16 Req per seconds. That seems very slow. Is there any way to improve the performance?

[jsccast]

How are you running the load test? What platform?

[rakesh-roshan]

I am using a linux ubuntu 16.04 machine. I am using https://github.com/rakyll/hey to generate a load. I noticed one more thing. After my load testing script ended pushing events to the rulio, the rulio's CPU usage remained very high even though no events being pushed to the service.

[rakesh-roshan]

I am using cassandra backend. But it seems to me that, it is accessed on loading the rules. But on each event, the server doesn't go to cassandra.

[jsccast]

If you can, try another persistence method to get started. The Cassandra support hasn't gotten much attention recently.

[rakesh-roshan]

I tried with default storage. The usage remained very high.

[jsccast]

Have you tried the little simulator in tools/sim?

Example output:

latencies,104,64.000000,64,1,3,6,7,21,2
latencies,105,58.000000,58,2,3,4,4,5,0
latencies,106,71.000000,71,1,2,3,5,6,0
latencies,107,66.000000,66,2,3,3,4,5,0
latencies,108,65.000000,65,1,3,3,5,6,0
latencies,109,63.000000,63,2,3,3,4,7,0
latencies,110,68.000000,68,1,2,3,5,9,1
latencies,111,63.000000,63,2,3,3,7,10,1
latencies,112,64.000000,64,1,3,3,5,6,1
latencies,113,66.000000,66,1,2,3,3,4,0
latencies,114,70.000000,70,2,3,4,10,12,1
latencies,115,61.000000,61,1,3,8,9,15,2
latencies,116,62.000000,62,2,3,4,6,7,1

Most of those numbers are milliseconds, which is a good starting point.

What do you see there?

What rules and events are you using in your tests?

[roneetshaw]

Any solution to high CPU usage?

[rakesh-roshan]

Hi Roneet, I am sorry, I didn't find a solution to that problem.

…

-- Rakesh

On Wed, Apr 22, 2020 at 10:51 AM Roneet Shaw ***@***.***> wrote: Any solution to high CPU usage? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#46 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJFN6YT4Z7BYN3I3QPR3ELRN4AAXANCNFSM4FUCFLVA> .