search

noahd1 / oink

Log parser to identify actions which significantly increase VM heap size
MIT License
1.18k stars 71 forks source link

any way to show the delta used for the threshold? #9

Closed inspire22 closed 13 years ago

inspire22 commented 13 years ago

The results show the total memory when that request was made, but it would be more useful to know that this request caused the total memory to go up by 25MB. Since you're already generating it to use the threshold, would it be hard to add to the results printout?

inspire22 commented 13 years ago

Aah, it does in the regular mode, just not in the verbose mode.

noahd1 commented 13 years ago

Going to close this issue, but thanks for answering it.

Somewhat related - I wish Oink logged memory deltas instead of the total memory. This would making log parsing and reporting easier. The change is fairly easy for this but would involve some coordination with other projects that rely on oink's log format.

inspire22 commented 13 years ago

What other projects are there I should be checking out? :)

On Tue, May 10, 2011 at 5:25 PM, noahd1 reply@reply.github.com wrote:

Going to close this issue, but thanks for answering it.

Somewhat related - I wish Oink logged memory deltas instead of the total memory. This would making log parsing and reporting easier. The change is fairly easy for this but would involve some coordination with other projects that rely on oink's log format.

Reply to this email directly or view it on GitHub: https://github.com/noahd1/oink/issues/9#comment_1134888

Thank you Kevin Watt

noahd1 commented 13 years ago

heh, well request log analyzer is hinged currently on oink's log output: https://github.com/wvanbergen/request-log-analyzer