performance of chart for certain large log files should be improved about gcviewer

[whitmad]

This is a big problem for me - analysing GC log files for long-running processes, they get pretty big. GCViewer would be useful if it could do this.

[chewiebug]

Do you already experience low performance with your log files? What is "big" in your case? Would it be possible to send a sample log file to have more input for analysis (please zip and email to [email protected])?

Regards, Jörg

[whitmad]

Jörg

"Big" could be several hundred MB in a busy system over a sustained
period - unfortunately too big for our email system to send - is there a
URL I can upload an example to?

Regards,

David

On Mon, 2012-05-14 at 09:10 -0700, chewiebug wrote:

Do you already experience low performance with your log files? What is "big" in your case? Would it be possible to send a sample log file to have more input for analysis (please zip and email to [email protected]).

Regards, Jörg

---

Reply to this email directly or view it on GitHub:
#23 (comment)

[chewiebug]

Hi David,

Ok, several hundred MB definitely sounds big. I don't have an upload server to post files to, but other users have used http://www.dropbox.com to provide me with larger files. http://www.fileconvoy.com/index.php would be an alternative without the need to install anything. Can you use one of those two possibilities?

Regards, Jörg

[chewiebug]

Hi David,

I have pushed a few lines of code to the repository improving the performance. With the log files I have, performance is clearly better now, but none of my testfiles is larger than 100MB. Is it possible for you to use one of the above mechanisms to send me one of your files or could you test yourself and let me know the result?

Regards, Jörg

[chewiebug]

Having added a few performance improvements, I'll close this issue. If the problem persists, please tell me.

Regards, Jörg

[whitmad]

Apologies, Jörg, been a bit busy. I'll try and check this sometime this
week, also will upload a sample file as you requested.

On Sun, 2012-06-17 at 08:58 -0700, chewiebug wrote:

Having added a few performance improvements, I'll close this issue. If the problem persists, please tell me.

Regards, Jörg

---

Reply to this email directly or view it on GitHub:
#23 (comment)