GNU bug report logs - #66112
question about gzip timing

Previous Next

Package: gzip;

Reported by: "Azami, Noushin" <noushin.azami <at> txstate.edu>

Date: Wed, 20 Sep 2023 01:41:02 UTC

Severity: normal

To reply to this bug, email your comments to 66112 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to bug-gzip <at> gnu.org:
bug#66112; Package gzip. (Wed, 20 Sep 2023 01:41:02 GMT) Full text and rfc822 format available.
Acknowledgement sent to "Azami, Noushin" <noushin.azami <at> txstate.edu>:
New bug report received and forwarded. Copy sent to bug-gzip <at> gnu.org. (Wed, 20 Sep 2023 01:41:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: "Azami, Noushin" <noushin.azami <at> txstate.edu>
To: "bug-gzip <at> gnu.org" <bug-gzip <at> gnu.org>
Subject: question about gzip timing
Date: Tue, 19 Sep 2023 20:05:30 +0000

[Message part 1 (text/plain, inline)]
Hello,

I'm trying to run gzip on a set of inputs and I want to time the compression and decompression so I can calculate the throughputs. I want the comparison to other compressors that I'm timing to be fair, so I need to time only the compressor and decompressor functions and not the entire code.
Is there a way to do this easily? Could you please point me to where in the source code (.c codes) I should insert timers to measure this correctly?


Thank you,
Noushin Azami

[Message part 2 (text/html, inline)]
This bug report was last modified 227 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.