> Heap consumption and performance are real problems in Java.
But doesn't the JSL guarantee that an OutOfMemoryException is never thrown
until all non-reachable objects have been GC:ed? Why would the JVM though an
OutOfMemoryException without first doing a full GC?
--
/ Peter Schuller
PGP user
On Thu, 06 Jan 2000, Juergen Kreileder wrote:
> You should update your glibc first, the LinuxThreads library is still
> work in progress. E.g. the original glibc-2.1.2 release didn't pass
> sigcontext to user handlers, this was fixed in glibc-2.1.2 CVS tree as
> of 1999/10/24 (this is the versio
Hallo Michael,
MEM>that is good news.
MEM>i did alot of the same kind of testing.
MEM>i did "new Integer[100]"
MEM>and i never ran out of heap.
I did THAT one, too. I didn't run out of heap, too. But when using "new
Integer(0)" instead, it crashes - mind you, it doesn't run out of heap,
tho
> Michael E Moores writes:
Michael> ah, back to the same old problem. maybe i should get a phd in
Michael> compilers/linkers.
Michael> i suppose my best bet is to start by compiling everything
Michael> on the box with the same library path; including the jdk.
You should upda
ah, back to the same old problem. maybe i should get a phd in
compilers/linkers.
i suppose my best bet is to start by compiling everything
on the box with the same library path; including the jdk.
so when i dive into compiling the jdk when RC4 releases,
is the latest source available to do it?
that is good news.
i did alot of the same kind of testing.
i did "new Integer[100]"
and i never ran out of heap.
again, i want to look at what libraries your jdk is depending on.
i may have to point my cheap finger at glibc.
i have been using RC2/glibc1.2.1 cause my 3rd party
JNI interface cr
> Michael E Moores writes:
Michael> that is a valuable (non-political.. hee hee)
Michael> data point ekkehard.
Michael> so you must be using glibc2.1.2?
Michael> i am using mandrake 6.1, which uses glibc2.1.1,
Michael> so i have also been using JDK 1.2 RC2 to be compa
that is a valuable (non-political.. hee hee)
data point ekkehard.
so you must be using glibc2.1.2?
i am using mandrake 6.1, which uses glibc2.1.1,
so i have also been using JDK 1.2 RC2 to be compatible.
i wonder if glibc is causing some of the problesm?
i am also seeing some intermittent thre
tual=5072, free=2097144).
I think that this type of test is very important, because this show some really
conditions with really users.
Thanks for all.
Edson Richter
--
From: Ekkehard Kraemer
Sent: quarta-feira, 5 de janeiro de 2000 22:16
To: [EMAIL PROTECTED]
Subject: RE:
Hallo Edson Carlos Erickss,
some results for the Blackdown JDK 1.2.2 RC 3, native threads, sunwjit:
It does at least 80.000 loops without problems (I canceled it afterwards);
rt.free() is constantly 1048568 Bytes; the effective memory used by the
program is constantly 4520 K (+1024 K shared).
M
Hello Michael,
MEM>i think the jvm/jdk has a big leak with one or more of the
MEM>classes used.
I'm running the Blackdown JDK (1.2-RC3, with sunwjit and native threads) here
with very good results. I have only one (non-trivial) application running, and
it doesn't show your problem. It uses socke
FYI i am using native threads.
also, the garbage collection loop
ONLY tells the system we would like to encourage
a GC pass. i noticed that this DID make the
program have less periodic slowness..
At 08:40 PM 1/5/00 -0200, Edson Carlos Ericksson Richter wrote:
>For all: I'm doing a comparision b
E. Moores
>Sent: quarta-feira, 5 de janeiro de 2000 17:40
>To: Edson Carlos Ericksson Richter
>Cc: [EMAIL PROTECTED]
>Subject:RE: heap space and performance
>
>so you can also see the heap get used up
>with the win32 JDK?
>i don't see how the blackdown
For all: I'm doing a comparision based on report from Michael E. Moores using the same
program (see bellow) and anotating reports about memory usage (and, of course,
stability). Michael reported a crash after 45000 loops in Linux JDK1.2.2 ("linux 2.2,
blackdown 1.2 (glibc 1.2.1)").
My comparis
er
Cc: [EMAIL PROTECTED]
Subject: RE: heap space and performance
so you can also see the heap get used up
with the win32 JDK?
i don't see how the blackdown JDK can be used
for programs that persist for long periods.
i tried several versions of that code.
i agree you will al
C in Linux are not ok.
Edson Richter
--
From: Michael E. Moores
Sent: quarta-feira, 5 de janeiro de 2000 17:40
To: Edson Carlos Ericksson Richter
Cc: [EMAIL PROTECTED]
Subject: RE: heap space and performance
so you can also see the heap get used up
with the win32 JDK?
i
values, and so on, I'm developing a healt care app, and
>I know what about it. But Java (especially JSP and Servlets) is more
>stable (I can't guarantee Linux version) than Visual Basic (by example)
>and anyone take less errors coding in Java than C.
>
>[]s
>
>Edson
Heap consumption and performance are real problems in Java.
But some great pratices in coding solve (or amenizes) the problem:
1) Don't repeat declaration of common used variables:
2) Create a thread in your main class taking a "forced garbage collection".
See the following program, that I've r
i wonder if someone can provide some insight
on the garbage collection and heap size.
i wrote a program (below) in a loop
and recorded the response times and heap size.
when i started it, i was able to run the loop
125 times per second, using 11% CPU. after several minutes,
i ran out of memory (
19 matches
Mail list logo
