garbage collector - performance problem - Thread - go-pugleaf

Thread View: borland.public.jbuilder.java.swing

3 messages

[T] Back to Threads [V] Tree View [G] Group Articles

3 total messages Started by Zoran Pjevic Wed, 02 Mar 2005 13:35

garbage collector - performance problem

#581

Author: Zoran Pjevic
Date: Wed, 02 Mar 2005 13:35

29 lines
1892 bytes

Hello

I not sure that my question is related to Swing, but is is my best
guess.

We have an Swing based GUI which is on top of a C++ embedded
application which feeds data into a hardware unit.

In stress testing conditions under very high data rates everything
runs fine for up to 15 hours. But then occasionaly it happens that the
hardware gets a datadrop.

When the same test is performed without the GUI, this is not noticed.

So I suppose that the garbage collector is doing incremental
collecting for hours and hours and then when some limits are reached
it peforms some major collecting, which slows down the GUI and with it
the underlying C++ core.

If this is the case - is there any way to programmatically influence
the schema of how the garbage collector works or at least to get a
message from the garbage collector when it starts this major
collecting? Or can I force it to to do its job in the background?

Or do you think I am completely wrong with my interpretation of the
problem?

Thanks for any hints,
Zoran

Re: garbage collector - performance problem

#582

Author: Doychin Bondzhev
Date: Wed, 02 Mar 2005 16:11

37 lines
2340 bytes

try some other GC algorithm. THere is few of them in 1.4.1

Check in the 1.4 documentation for more details regarding different GC's 
available in Java 1.4.1 and above.

Doychin

Zoran Pjevic wrote:
> Hello
> 
> I not sure that my question is related to Swing, but is is my best
> guess.
> 
> We have an Swing based GUI which is on top of a C++ embedded
> application which feeds data into a hardware unit.
> 
> In stress testing conditions under very high data rates everything
> runs fine for up to 15 hours. But then occasionaly it happens that the
> hardware gets a datadrop.
> 
> When the same test is performed without the GUI, this is not noticed.
> 
> So I suppose that the garbage collector is doing incremental
> collecting for hours and hours and then when some limits are reached
> it peforms some major collecting, which slows down the GUI and with it
> the underlying C++ core.
> 
> If this is the case - is there any way to programmatically influence
> the schema of how the garbage collector works or at least to get a
> message from the garbage collector when it starts this major
> collecting? Or can I force it to to do its job in the background?
> 
> Or do you think I am completely wrong with my interpretation of the
> problem?
> 
> Thanks for any hints,
> Zoran

Re: garbage collector - performance problem

#584

Author: dar7yl
Date: Fri, 04 Mar 2005 02:44

38 lines
2279 bytes

"Zoran Pjevic" <zpjevic@anitesystems.de> wrote in message 
news:mdfb21hrbfafuvk3o6p7ormovgbj64cumo@4ax.com...
> Hello
>
> I not sure that my question is related to Swing, but is is my best
> guess.
>
> We have an Swing based GUI which is on top of a C++ embedded
> application which feeds data into a hardware unit.
>
> In stress testing conditions under very high data rates everything
> runs fine for up to 15 hours. But then occasionaly it happens that the
> hardware gets a datadrop.
>
> When the same test is performed without the GUI, this is not noticed.
>
> So I suppose that the garbage collector is doing incremental
> collecting for hours and hours and then when some limits are reached
> it peforms some major collecting, which slows down the GUI and with it
> the underlying C++ core.
>
> If this is the case - is there any way to programmatically influence
> the schema of how the garbage collector works or at least to get a
> message from the garbage collector when it starts this major
> collecting? Or can I force it to to do its job in the background?
>
> Or do you think I am completely wrong with my interpretation of the
> problem?
>
> Thanks for any hints,
> Zoran

Try calling System.gc() from your GUI application.
I've found if you call it on a periodic basis, major garbage collection
hesitations are minimized (but not eliminated entirely)

regards,
    Dar7yl

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads