Hi Alan,
we run our ELOG server (38 GB Logbook data in about 50 logbooks dating back up to 16 years) on a virtual Linux box.
The memory is important, since ELOG scans through all entries and creates an index at start-up. But we have only about 6% used out of 2GB: ELOG is not very demanding. If you have many and large pictures attached, then "convert" needs a bit of memory to work with.
Since "elogd" is a single task, you will not gain much from many CPUs. File IO is often a limiting factor: we've tried a while to run the logbook data on an AFS directory, and that did not turn out well. A local disk is best, an NFS disk works fine as well (in our case).
Cheers, Andreas
| Alan Grant wrote: |
|
In response to an elog-hang issue I've been having on the Windows platform, I am building a new Unbuntu 14 TLS VM machine to host the identical configuration so that I can more easily debug when the hang happens again. I don't mind beefing up the hardware resources to either eliminiate that as a factor or resolve the problem. I'll have a higher end CPU to deal with 20 to 50 clients doing searches through the data (since the elog configuration currently does not provide a setting to limit how far back it can search with Quick Filters - pretty please add this basic setting!), but the main question I have now is what is a good amount of memory to add to the VM? I suspect even with 30 concurrent searches going CPU power will have more impact than memory in the case of elog. Can someone please confirm my suspicion and also recommend a suitable amount of memory I should install? My data volume is about 25 MB, all textual (no attachmemts), and the number of daily files goes back about 5 years. Any other tips for the build is very welcome.
|
|