Solaris (and any other operating system) will segregate different memory for
each process that is running. In this case each instance of Analog that you
start is independent and will run as its own process so the memory they use is
segregated.
Analog is compiled in 32-bit mode by default and therefore can only reach 4GB
of memory. If you re-compile in 64-bit mode (there are directions in the make
file and possibly binaries in ports) then it can access more than 4GB of RAM
(18 exabytes theoretically).
I don't know a whole lot about how Solaris works, but guessing from their
documentationhttp://docsun.cites.uiuc.edu/sun_docs/C/solaris_9/SUNWdev/SOL64TRANS/p5.html,
it allocates one 32-bit virtual machine for all 32-bit apps, so multiple
32-bit versions of Analog will be fighting for the same 4GB of memory.
--
Jeremy Wadsack
Seven Simple Machines
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Terry Chambers
Sent: Wednesday, August 13, 2008 7:32 AM
To: analog-help@lists.meer.net
Subject: [analog-help] Running multiple reports on the same server
We have a powerful Solaris server that has Analog installed on it (32GB of
RAM). I have read the threads and it seem that Analog will only use 4GB of RAM
unless you recompile it and change the memory settings.
I am wondering what would happen if we ran Analog multiple times on the server.
So far I have built configs and command lines for 5 different reports that I'd
like run daily but I am scheduling them at intervals to prevent any issues.
Any thoughts / opinions? Will multiple instances use the same 4GB of RAM or
will the O/S distribute it out evenly?
Thanks
Terry
+
| TO UNSUBSCRIBE from this list:
|http://lists.meer.net/mailman/listinfo/analog-help
|
| Analog Documentation: http://analog.cx/docs/Readme.html
| List archives: http://www.analog.cx/docs/mailing.html#listarchives
| Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
+