Skip to content
This repository has been archived by the owner on May 17, 2021. It is now read-only.

performance enhancements #238

Open
katmai opened this issue Aug 14, 2016 · 7 comments
Open

performance enhancements #238

katmai opened this issue Aug 14, 2016 · 7 comments

Comments

@katmai
Copy link

katmai commented Aug 14, 2016

hi,

i have been playing with this for about 2 weeks now on a 12 cores xeon server with 64 gigs ram.

is there any way you could like improve the resource usage? when running commands like minicron server start or when i look under the usage this thing works like a pig. i got 2.5 gb ram used to manage some 30 cron jobs.

i really like the interface and stuff but could you optimize the thing a little bit better? the thing is i don't know if this is a ruby thing - i hate ruby but it would be nice if it didn't require a spaceship to run some cronjobs

thanks.

@jamesrwhite
Copy link
Owner

Is that 2.5 GB ram usage coming from the process that is running the server or the jobs themselves?

@katmai
Copy link
Author

katmai commented Aug 25, 2016

it's coming from the process running the server. i just looked now and it seems to be going up to 12 gigs. i got 64 gb ram on this server so it's not really causing issues right now, but 12 gb ram for a cron job manager is kinda eek. if i restart it, it will go down and start chewing up ram again, like Chrome. i just left it like this so we can debug or maybe improve w/e.

12852 root 20 0 11.780g 0.011t 5240 S 4.3 18.3 1009:54 ruby

@jamesrwhite
Copy link
Owner

Does the memory usage steadily increase after a restart? It might be a memory leak as opposed to just general inefficiency.

@katmai
Copy link
Author

katmai commented Sep 6, 2016

dang, i missed your reply.

and yes, the memory usage increases slowly after a restart. i restarted it at 12gb 12 days ago, and now it's back at 10 gb once more and going up:
5160 root 20 0 10.486g 0.010t 5256 S 11.0 16.3 934:25.47 ruby

i am running centos 7.2 64bit.

@katmai
Copy link
Author

katmai commented Sep 10, 2016

rocking a good 13 gb ram used now:

5160 root 20 0 12.761g 0.012t 5256 S 1.3 19.9 1193:34 ruby

@katmai
Copy link
Author

katmai commented Sep 30, 2016

5160 root 20 0 23.112g 0.022t 4844 S 7.0 36.4 2175:48 ruby
went to 23 gb.

do you want to test anything or?

@katmai
Copy link
Author

katmai commented Nov 2, 2016

i was checking the db and i noticed that the interface was getting considerably sluggish as the job executions count went up - i had over 600 k and it was working like a pig. so i emptied that table and job_execution_outputs which was hitting 1.5 gb on 11 mil rows and now the thing is speedy

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants