Too much Java for one PC

7 PM May 19, 2005

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:

  • 1 Kiosk (70–100Mb)
  • 1 Central controller (70–100Mb)
  • A test load generator (70–100Mb)
  • Chainsaw, for viewing logs (50–250Mb)

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.

By alang | # | Comments (7)
(Posted to javablogs and Java)


At 23:59, 19 May 2005 Anjan Bacchu wrote:

hi there,

  how about resin ? Resin is GPL and unless you're shipping it , you can use it internally for commercial purposes.


At 00:53, 20 May 2005 Jed Wesley-Smith wrote:

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 ...

At 03:53, 20 May 2005 Andy Todd wrote:

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.

At 18:43, 20 May 2005 ahmetaa wrote:

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..

At 00:20, 21 May 2005 Kirk wrote:

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.... :)

At 20:15, 21 May 2005 Paulo Gaspar wrote:

For a much smaller footprint, single file BD, online backups, transactional, triggers, really easy install, multiple OS support:

At 09:40, 22 May 2005 Alan Green wrote:

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.


Add Comment

(Not displayed)

(Leave blank line between paragraphs. URLs converted to links. HTML stripped. Indented source code will be formatted with <pre> tags.)

© 2003-2006 Alan Green