Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : All About Sun Microsystems -- Ignore unavailable to you. Want to Upgrade?

To: JC Jaros who wrote (23369)	11/24/1999 9:34:00 PM
From: Robert	Respond to of 64865

Have a look at: javaworld.com "Moreover, Table 2 shows that, with the exception of TowerJ 3.1.4 for Linux, VMs for Linux seem particularly susceptible to poor scalability results, a problem Neffenger blames on an incompatibility between Java's I/O model and the Linux model. "I'm disappointed in the network scalability on Linux. IBM on Linux couldn't even do the test. The solution is to do a different threading model for Java on Linux, similar to the TowerJ solution, or better, as Sun did on Solaris," he states. The scalability problem revealed by the VolanoMark tests comes down to a conflict between how Java handles threads and sockets and how the underlying operating systems handle them, says Neffenger. Java, for instance, requires one or two dedicated threads in order to read and write data from a socket connection. On the operating systems side, the Windows platform limits the number of threads handled in a single process, while Unix-based systems limit the number of sockets you can give to a single process (because of the file descriptor limits). If the VM vendor isn't careful, this incongruity can result in runtime errors at increasing concurrent connection levels. "