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 : CYRIX / NSM -- Ignore unavailable to you. Want to Upgrade?

To: Scumbria who wrote (26055)	4/20/1998 1:30:00 AM
From: Joe NYC	Read Replies (1) \| Respond to of 33344

Scumbria, Just try this: Make sure you have some caching on in your browser. Go to a site with the Java applet, make sure it executes once. Go to some other site and go back. At least in IE4, the Java VM stays loaded and initialized, java applet code is cached, and execution is almost instantaneous (on my P166+). Joe

To: Scumbria who wrote (26055)	4/20/1998 1:34:00 AM
From: FJB	Read Replies (1) \| Respond to of 33344

Scumbria, I consider multiple threads to occur within what you are naming the execution part of three threads. Perhaps, we are talking about different things? For example, compilation occurs before execution and garbage collection occurs after a thread has been executed. When I think of multi-threaded applications I think of the OS allocating CPU time for several programs that were written to take advantage of this feature. Bob

To: Scumbria who wrote (26055)	4/20/1998 11:10:00 AM
From: Steve Porter	Read Replies (1) \| Respond to of 33344

Scumbria, Are you ON CRACK? Garbage collection (which is very inefficient in Java FYI Java has one of the most efficient grabage collection engines in the history of computing... You really should read more about the technical details of the language. Recent studies show that garbage collection takes only 15% of Java's execution time. Previous attempts at garbage colleciton have been on the order of 35-40%. The big bottle neck in Java is dynamic class loading and companies like borland are already addressing that... class loading has nothing to do with the garbage collector. Also which JVM and JIT are you using.. if it's the netscape one, no wonder your performance sucks.. it's 40% slower than the MS one.. Steve Cyrix/NSM Rule!