Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Blitz.io after effects
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Blitz.io after effects

fresher_06fresher_06 Member
edited November 2012 in General

Recently i ran benchmark stuff from Blitz.io and got this results --

11,980 successful hits in 1.0 min and we transferred 47.94 MB of data in and out of your app. The average hit rate of 194/second translates to about 16,816,414 hits/day

But after that my memory usage has gone really high and its not at all coming down. I have restarted nginx and php5-fpm .. still showing as below --

Mem: 327680k total, 321808k used, 5872k free, 0k buffers
Swap: 0k total, 0k used, 0k free, 306500k cached

Comments

  • 15mb RAM usage, whats wrong with that?

  • @gsrdgrdghd -- 15mb .. whereis that .. its showing 321808k used .. which is approx .. 321MB of RAM

  • gsrdgrdghdgsrdgrdghd Member
    edited November 2012

    Yeah but 306500k of that is just caches which will be emptied if needed...

  • Have you seen this: http://www.linuxatemyram.com/?

  • jarjar Patron Provider, Top Host, Veteran
    edited November 2012
  • "Free" Ram, is Wasted Ram.

  • @fresher_06 said: 194/second

    Mind sharing your config and specs?

  • @kamalnasser . I am running .. on 256 Main memory and 64MB vswap . on 4 core cpu .. ..also just running nginx,mysql and php-fpm .. all installed by https://github.com/Xeoncross/lowendscript

  • kbeeziekbeezie Member
    edited November 2012

    Gota love auto-installers the bane of learning.

    Simply put, MySQL+PHP on less than 512MB isn't going to fare well with higher blitz.io rushes, you'll want more ram depending on the kind of applications you're running. Nginx on the other hand would do just fine by itself for static content under 128 just fine.

    Also if you have 4 cores provided to you, you should be able to make sure the nginx workers listed at the top of nginx.conf is 4, as opposed to 1 or 2 (worker per core).

    Though needless to say ~194hit/sec isn't too shabby if you're not constantly erring out. What was the concurrency (max number of users) and timeout you set on your 1 minute blitz rush, and what type of page were you targeting?

    Also what do you get for static html rushes? (I've gotten up to 600r/sec on a 512MB openvz debian vps before: http://kbeezie.com/view/nginx-protection/ )

    Also as others have said, cached memory isn't gona go anywhere until you reboot the server. It sits there holding the information that was filled during the rush incase it's needed again, or it gets flushed in favor of new content, it'll almost be filled to some degree but not necessarily "out of memory".

Sign In or Register to comment.