Comments on: memCron 0.3

By: Bret

Bret — Mon, 20 Jul 2009 14:36:47 +0000

Ask DreamHost support to install it on your server.

By: Jiameng

Jiameng — Sun, 19 Jul 2009 06:07:07 +0000

I got this error message, how to deal with it?

501 Protocol scheme ‘https’ is not supported (Crypt::SSLeay not installed)Aborting at /home/lvya/eswnman.com/memcron/memcron.pl line 235.at /home/lvya/eswnman.com/memcron/memcron.pl line 235

By: David

David — Mon, 13 Jul 2009 15:10:24 +0000

Just a note to let you know that this app is great. It should really be in the DH panel, I hope they buy it from you and make it part of their core services.

By: Yaosan

Yaosan — Mon, 29 Jun 2009 01:26:52 +0000

memCron 0.4 has been released. Please give it a try and let me know how well it works, thanks!

By: Yaosan

Yaosan — Sat, 27 Jun 2009 20:06:05 +0000

Hi Zack, the discrepancy is due to a memory sizing bug during downsize operation. This bug has been fixed in the latest version, which will be release either later today or tomorrow.

Thanks for your bug report, they’re always helpful to make memCron better and better.

By: Zack

Zack — Sat, 27 Jun 2009 13:10:02 +0000

Something strange is happening. The graph is showing the total memory as 538MB while Dreamhost panel (as well as the ‘free’ command) show it as 626MB. Why the discrepancy?

By: Zack

Zack — Fri, 26 Jun 2009 18:54:59 +0000

This is good. I just started using it today and like it so far.

It looks like the two features (email when mem increases some threshold and max memory to allocate) I was interested in have already been coded for the next version which is great.

By: Craig

Craig — Fri, 26 Jun 2009 16:29:36 +0000

You are sooooooooo awessome

By: Yaosan

Yaosan — Fri, 26 Jun 2009 15:06:20 +0000

Thanks Bret, I’m glad memCron is working great for you. You’re right that the memory setting can be tweaked to reserve more memory. For memCron, the parameter you should look into is $mem_free_to_used_ratio.

With that said, I’m pretty confident that the default value of 1.2 should work well for most users. With a free to used ratio of 1.2, it will take a memory spike that raises your memory usage 2x within 5 minutes to bring down your server. For those who want more safety margin, feel free to increase the ratio but that extra margin do come with a price.

btw, if you somehow reduces your free to used ratio to save some server cost, the $mem_free_confidence will kick in when the standard deviation increases due to a spike. So yeah, you’re double protected by both parameters, pretty much.

By: Yaosan

Yaosan — Fri, 26 Jun 2009 14:56:17 +0000

Just an update on the progress. I manage to work extra hours yesterday and I think I have the min, max cap and threshold setting working. Now I just need to run the test on my own PS and if everything works smoothly I’ll have the new version released this weekend.