Status: New
Owner: ----
New issue 748 by [email protected]: verify scaling of inotify in luxid
http://code.google.com/p/ganeti/issues/detail?id=748
luxid currently watches all running jobs via inotify. While
this is the most efficient way for small values of
--max-running-jobs, for huge values of --max-running-jobs
it probably is better to only periodically scan all running
jobs for updates.
Note: WatchJob luxi requests are not affected, as they use their
own inotify instance anyway.
The onTimeWatcher in JQScheduler already provides this
functionality, so implementation-wise, the only task to
make the "mapM_ (attachWatcher qstate) chosen" in scheduleSomeJobs
depend on the value of getMaxRunningJobs. The main task, however,
is to find a suitable value on when to not attach an inotify.
So we should do corresponding load tests before the release of 2.12.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
