which is the different parameter used to evaluate for performance of compression algorithm?

Question

2.00/5 (1 vote)

See more:

please give me some parameter which is used to evaluate the performance of compression algorithm

tell me how it is used to valuate...

please help
thanks

Posted 11-May-12 3:24am

PKriyshnA

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

CPallini · Answer 1 · 2012-05-11T03:35:00

Solution 2

Given a set of suitable input data, there are essentially these paramenters: the compression ratio (size_after_compression/size_before_compression) and both the compression and decompression speed (bytes/sec).

Posted 11-May-12 3:35am

CPallini

Updated 11-May-12 23:01pm

v3

Comments

Sergey Alexandrovich Kryukov 11-May-12 18:02pm

Important note: in this answer, last '/' character is not a division operator, because otherwise 1) slow decompression speed would mean good algorithm; 2) infinitely slow decompression (thread never completes, due to a programming bug, zero decompression speed) would cause division by zero; in floating-point arithmetic it would produce quality equal to +Infinity. :-)
My 5. :-)
--SA

CPallini 12-May-12 5:00am

It was indeed confusing, I've changed that.
BTW Thank you.

Sergey Alexandrovich Kryukov 14-May-12 15:31pm

You are welcome.
I did not actually think it was confusing; I just tried to joke about it, picturing some stupid reader who could possibly think that '/' could be a division operator :-)
However, this joke was inspired by the real-life experience with some inquirers here at CodeProject... :-)

Cheers,
--SA

Bernhard Hiller · Answer 2 · 2012-05-11T03:34:00

When it comes to loss-less compression (i.e. compressing a file for storage), then the main point is compressed file size divided by original file size, followed by the time required for compression.
Sometimes, a lossy compression is used, e.g. jpg for images, or mp3 for audio. Here, a measurement for loss is required, but that is harder to describe, because in the end the result is evaluated by a human user who has to see a nice picture or listen to "high-fidelity" music.