From: "Nitin Gupta" <nitingupta910@gmail.com>
To: "Pavel Machek" <pavel@ucw.cz>
Cc: "Richard Purdie" <richard@openedhand.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Michael-Luke Jones" <mlj28@cam.ac.uk>,
linux-kernel@vger.kernel.org, linux-mm-cc@laptop.org
Subject: Re: [RFC] LZO de/compression support - take 3
Date: Sat, 26 May 2007 16:47:30 +0530 [thread overview]
Message-ID: <4cefeab80705260417h43d4d8a9s3f55b7eb3c19396c@mail.gmail.com> (raw)
In-Reply-To: <20070525104253.GA4555@ucw.cz>
Hi Pavel,
Just did some benchmarking; results below.
On 5/25/07, Pavel Machek <pavel@ucw.cz> wrote:
>
> What is the performance difference between safe and unsafe version?
>
File size: 256K
- Following as tests for original test code - not any kernel port of this.
- Test with each block size repeated 5 times - taken avg. of these 5 runs.
- Same file used for each test.
- Used lzotest utility (included with LZO 2.02) for testing.
Blocksize Comp* DU* DS* Speed%
4 59.356 211.526 195.260 7.689
8 54.623 202.712 188.369 7.075
16 50.342 196.482 183.988 6.358
32 47.499 189.800 177.455 6.504
64 44.148 178.724 167.201 6.447
128 42.125 170.229 159.257 6.445
256 41.830 155.035 146.115 5.753
* All speeds in MB/sec
Comp = LZO1X-1
DU = Decompress (unsafe)
DS = Decompress (safe)
Speed% = ((DU-DS)/DU)*100
I have yet to see how the kernel ports compare against this original version.
Cheers,
Nitin
next prev parent reply other threads:[~2007-05-26 11:17 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 8:27 [RFC] LZO de/compression support - take 3 Nitin Gupta
2007-05-23 10:53 ` Michael-Luke Jones
2007-05-23 11:39 ` Nitin Gupta
2007-05-23 13:57 ` Michael-Luke Jones
2007-05-23 14:03 ` Nitin Gupta
2007-05-23 14:10 ` Michael-Luke Jones
2007-05-23 14:21 ` Nitin Gupta
2007-05-23 14:33 ` Michael-Luke Jones
2007-05-24 22:41 ` Richard Purdie
2007-05-24 22:54 ` Andrew Morton
2007-05-24 23:00 ` Richard Purdie
2007-05-23 16:16 ` Andrew Morton
2007-05-23 16:49 ` Richard Purdie
2007-05-24 4:04 ` Nitin Gupta
2007-05-25 10:42 ` Pavel Machek
2007-05-26 10:23 ` Michael-Luke Jones
2007-05-26 11:17 ` Nitin Gupta [this message]
2007-05-23 14:50 ` Bret Towe
2007-05-24 13:48 ` Nitin Gupta
2007-05-25 2:38 ` Bret Towe
2007-05-25 5:10 ` Nitin Gupta
2007-05-25 17:02 ` Bret Towe
2007-05-25 17:33 ` Nitin Gupta
2007-05-26 11:30 ` Nitin Gupta
2007-05-27 3:39 ` Bret Towe
2007-05-23 19:34 ` Satyam Sharma
2007-05-24 4:37 ` Nitin Gupta
2007-05-24 10:49 ` Satyam Sharma
2007-05-24 8:25 ` Richard Purdie
2007-05-24 11:07 ` Satyam Sharma
2007-05-24 14:29 ` Nitin Gupta
2007-05-24 19:12 ` Satyam Sharma
2007-05-24 14:20 ` Nitin Gupta
2007-05-24 20:09 ` Satyam Sharma
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4cefeab80705260417h43d4d8a9s3f55b7eb3c19396c@mail.gmail.com \
--to=nitingupta910@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm-cc@laptop.org \
--cc=mlj28@cam.ac.uk \
--cc=pavel@ucw.cz \
--cc=richard@openedhand.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.