Thanks, Carl, The information really helps. I installed BASE but I am not the root user of the BASE. That is why I tried to find somewhere on the Linux machine to change the memory allocation. The different amount of RAMs allowed for one job doesn't make significant differences on small scale data (in my case, 1 million data points). So the default settings should work fine for most single lab usage. Thanks again and wish you all a good time. Zhilin
________________________________ From: [EMAIL PROTECTED] on behalf of Carl Troein Sent: Tue 2/21/2006 3:58 AM To: basedb-users@lists.sourceforge.net Subject: Re: [base] Help needed on jobRunner Liu, Zhilin (UMC-Student) wrote: > By the way, Carl, could you explain a little bit more about how the memory > usage is > controlled in plugins? I have read your note on 2005-03-02, but didn't quite > get it. In > my case, I have only one machine, with 6G memory. In PHP, I set the memory > limit to > 1.5G. However, in BASE, for example, for the plugin "pinbased_lowess", I can > only set > 128M memory to it. Whenever I increase the number, I got the error message > same as > Etienne got "Aborted by jobManager: No computation servers are capable of > running this > job. Limiting factor(s): RAM". How can I solve this problem? Thanks in > advance. In "Analyze data" -> "Computation servers" you can find the machine called "Local". Edit it, and change the "Total RAM available for jobs" to something much bigger. This is a case of a) this aspect of BASE needing more/better documentation, and b) the default value being unreasonably low. In short, the job system works like this now: There are a number of slots that may be used by plugins, and they're associated with different plugin runtimes (estimated or reached), so that the system tries to mix fast and slow plugins in a good way. On top of this is the RAM thing, where each computation server (normally only one: the BASE server itself) has an amount of RAM that jobs may use, and a small fraction of this is reserved for each slot while the rest can be grabbed by jobs that may need it. It is difficult to estimate how much RAM a plugin will use, because we can't know how much it has used in the past (better resource usage statistics from the operating system would be required for this), so we leave it to the admin and user to handle this manually. It would probably make sense to not have any limits by default, though, even if that means that an ill- behaved plugin could possibly crash the BASE server (which is a testament to how badly Linux still handles out-of-memory situations, and how much we need more fine-grained resource management). //Carl -- Carl Troein - [EMAIL PROTECTED] http://www.thep.lu.se/~carl/ ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ The BASE general discussion mailing list basedb-users@lists.sourceforge.net unsubscribe: send a mail with subject "unsubscribe" to [EMAIL PROTECTED]
<<winmail.dat>>
