<a href="http://forums.hotjoe.com/forums/list.page" target="_blank" rel="nofollow">Java forums using Java software</a> - Come and help get them started.
Originally posted by William Brogden:
Instead of multiple instances of Tomcat consider running the application in a separate JVMs, communicating with Tomcat by RMI, JMS, JavaSpace or sockets. That way you can add processing power elsewhere on your network as needed.
Bill
Originally posted by Scott Dunbar:
You don't tell us your JVM or O/S but the Sun JVM seems to be limited to about 1.5GB under Windows, 2GB under Solaris x86 and Linux, and 4GB under Solaris SPARC. These are all 32 bit JVM's. Under Solaris it seems likely that if you used some O/S specific settings (ISM) you should be able increase it. I have not seen what the max is under Sun's 64bit JVM's.
Based on what you're saying it sounds like you may need to run multiple instances depending on your load and your platform.
<a href="http://forums.hotjoe.com/forums/list.page" target="_blank" rel="nofollow">Java forums using Java software</a> - Come and help get them started.
Originally posted by Scott Dunbar:
With those large of memory requirements I'd encourage you to carefully consider your design and deployment options. I do understand that rendering can take a boat load of memory but what you're describing sounds pretty high. Certainly you don't want to do the work more than once and you don't want to copy that much data over the network.
Originally posted by Scott Dunbar:
If you really can't split up the processing you're really going to need to consider a 64 bit JVM. After I responded to you before I did some digging. Under Solaris/SPARC with the 64 bit JVM people have reported allocating 32GB with no problem. I don't know the actual maximum but you may have to rethink your deployment platform.
Originally posted by jhon Reader:
i heard for jdk 1.5 ,
sun has tested it for 500 gb of ram
check it out if it is correct
All ideas will be taken in consideration, because the memory is really important key factor. But i don't quite understand what you mean, so is there any docs about this, or can you be a little bit more detailed in what you mean.
Originally posted by William Brogden:
A recent web seminar at jini.org titled Distributed Image Reformation Using JavaSpaces Technology may be a good introduction.
I actually have a micro example of distributed processing using a JavaSpace running on my web site. This page talks a bit about JavaSpaces and has a link to the demo. Instances of a phonetic lookup application are running on various places in my network, each one has a different dictionary in memory for speed in lookup. Each instance has registered with a JavaSpace as being able to take certain classes of phonetic lookup job. I would be glad to provide more details.
Bill
Originally posted by Mike Curwen:
my mind is boggling.
... now it's 1,5min with 250 MB used for 1 client. So now we are at a point where performance is acceptable (and really high) with as less as possible memory used.
1.5 minutes per request, and 250MB per user is both acceptable and the least memory possible?
Recognizing that not all apps are built alike, and admiting I've never worked on big-iron enterprise apps... I find it hard to understand how it's possible to have 250MB of data that is completely non-shareable and critical to retain 'in memory'.
Two questions I'd ask myself:
1) Is there absolutely no data in that 250MB that can be shared between all users?
2) Have I investigated the usage of a data abstraction/querying/caching layer enough?
- so if i got three worker-pcs i will also need 3 licenses of the rendering-software , and 1 license costs about 15000 dollar
Originally posted by William Brogden:
My little demo with phonetic coding starts three worker Threads, each one reads a particular dictionary of words, then tells the space manager (which can live on the same or different machine) that it is ready to look up words from a particular dictionary.
Bill
What's then the difference between those JavaSpaces and 1 pc with 3 or more instances of Tomcat with a load balancer in front of them ???
Consider Paul's rocket mass heater. |