At work, we’re looking for ways to reduce memory usage. Our development PCs are straining at the sides, even with 1Gb of memory.
The distributed system we are building will deploy with two central controller processes and fify kiosk processes. For developer testing, we run a smaller configuration:
Makes me pine for a simple, light-weight J2EE architecture.
Add in WebSphere MQ and the normal Windows cruft, and 1Gb is barely enough memory for this job. As Keith mentioned, we’re moving from WebSphere Express to Jetty. We’re also changing from Hypersonic SQL to MS SQL Server, which saves us another 30 to 50Mb.
Comments
hi there,
BR,
~A
they want to use Jetty as they are good Aussies and supporting the local product !-)
I recently moved up to a 2GB machine and I'm already running out of memory again ...
Nooooooo. Not SQL Server. Still, it can't be worse than Hypersonic. But then you knew I was going to say that.
If you want a lighter weight fully featured RDBMS with multi user access Firebird gets a good rap.
do not use HSQL in in-memory mode for big DB's (default is in-memory). Use cached-tables, so you can limit the memory as you wish..
I'm off in few minutes to buy 2x1 gig sticks of DDR2 for just over $200USD. At that price it just not worth spending a whole lot of time trying to use less 'cos it will just cost you a whole lot more to do so.... :)
Wy MSSQL?
For a much smaller footprint, single file BD, online backups, transactional, triggers, really easy install, multiple OS support:
http://firebird.sourceforge.net/
We're only using SQL Server because that is the client's preferred deployment platform. Since we have to get it working in the test environment, we may as well develop with it too.