view release on metacpan or search on metacpan
benchmark/benchmark.html view on Meta::CPAN
<td class="twofish">71706.42</td>
<td class="twofish">4481.65</td>
</tr>
</tbody>
</table>
<hr />
<p>
Remarks:<br />
<dl>
<dt><a name="lang">[1]</a></dt>
<dd>Some modules, like Crypt::DES_EEE3 or Crypt::DES_EDE3 are actually
pure Perl modules but are implemented as a wrapper around XS modules.
These are still listed here as implemented in C.
<a href="#top">back</a></dd>
<dt><a name="keys">[2]</a></dt>
<dd>One test cycle for key generation actually consists of a constructor
call followed by one encryption resp. decryption operation, since a module
may decide to postpone the key scheduling until the direction is fixed.
The number is therefore an indicator for the encryption/decryption
performance for small chunks of data.
benchmark/benchmark.pl view on Meta::CPAN
}
$html .= <<EOF;
</tbody>
</table>
<hr />
<p>
Remarks:<br />
<dl>
<dt><a name="lang">[1]</a></dt>
<dd>Some modules, like Crypt::DES_EEE3 or Crypt::DES_EDE3 are actually
pure Perl modules but are implemented as a wrapper around XS modules.
These are still listed here as implemented in C.
<a href="#top">back</a></dd>
<dt><a name="keys">[2]</a></dt>
<dd>One test cycle for key generation actually consists of a constructor
call followed by one encryption resp. decryption operation, since a module
may decide to postpone the key scheduling until the direction is fixed.
The number is therefore an indicator for the encryption/decryption
performance for small chunks of data.
benchmark/benchmark_by_blksize.html view on Meta::CPAN
<td class="other">640746.41</td>
<td class="other">80093.30</td>
</tr>
</tbody>
</table>
<hr />
<p>
Remarks:<br />
<dl>
<dt><a name="lang">[1]</a></dt>
<dd>Some modules, like Crypt::DES_EEE3 or Crypt::DES_EDE3 are actually
pure Perl modules but are implemented as a wrapper around XS modules.
These are still listed here as implemented in C.
<a href="#top">back</a></dd>
<dt><a name="keys">[2]</a></dt>
<dd>One test cycle for key generation actually consists of a constructor
call followed by one encryption resp. decryption operation, since a module
may decide to postpone the key scheduling until the direction is fixed.
The number is therefore an indicator for the encryption/decryption
performance for small chunks of data.
benchmark/benchmark_by_dblocks.html view on Meta::CPAN
<td class="other">1536.95</td>
<td class="other">96.06</td>
</tr>
</tbody>
</table>
<hr />
<p>
Remarks:<br />
<dl>
<dt><a name="lang">[1]</a></dt>
<dd>Some modules, like Crypt::DES_EEE3 or Crypt::DES_EDE3 are actually
pure Perl modules but are implemented as a wrapper around XS modules.
These are still listed here as implemented in C.
<a href="#top">back</a></dd>
<dt><a name="keys">[2]</a></dt>
<dd>One test cycle for key generation actually consists of a constructor
call followed by one encryption resp. decryption operation, since a module
may decide to postpone the key scheduling until the direction is fixed.
The number is therefore an indicator for the encryption/decryption
performance for small chunks of data.
benchmark/benchmark_by_dbytes.html view on Meta::CPAN
<td class="other">1536.95</td>
<td class="other">96.06</td>
</tr>
</tbody>
</table>
<hr />
<p>
Remarks:<br />
<dl>
<dt><a name="lang">[1]</a></dt>
<dd>Some modules, like Crypt::DES_EEE3 or Crypt::DES_EDE3 are actually
pure Perl modules but are implemented as a wrapper around XS modules.
These are still listed here as implemented in C.
<a href="#top">back</a></dd>
<dt><a name="keys">[2]</a></dt>
<dd>One test cycle for key generation actually consists of a constructor
call followed by one encryption resp. decryption operation, since a module
may decide to postpone the key scheduling until the direction is fixed.
The number is therefore an indicator for the encryption/decryption
performance for small chunks of data.
benchmark/benchmark_by_dkeys.html view on Meta::CPAN
<td class="other">14600.00</td>
<td class="other">1825.00</td>
</tr>
</tbody>
</table>
<hr />
<p>
Remarks:<br />
<dl>
<dt><a name="lang">[1]</a></dt>
<dd>Some modules, like Crypt::DES_EEE3 or Crypt::DES_EDE3 are actually
pure Perl modules but are implemented as a wrapper around XS modules.
These are still listed here as implemented in C.
<a href="#top">back</a></dd>
<dt><a name="keys">[2]</a></dt>
<dd>One test cycle for key generation actually consists of a constructor
call followed by one encryption resp. decryption operation, since a module
may decide to postpone the key scheduling until the direction is fixed.
The number is therefore an indicator for the encryption/decryption
performance for small chunks of data.
benchmark/benchmark_by_eblocks.html view on Meta::CPAN
<td class="other">1536.95</td>
<td class="other">96.06</td>
</tr>
</tbody>
</table>
<hr />
<p>
Remarks:<br />
<dl>
<dt><a name="lang">[1]</a></dt>
<dd>Some modules, like Crypt::DES_EEE3 or Crypt::DES_EDE3 are actually
pure Perl modules but are implemented as a wrapper around XS modules.
These are still listed here as implemented in C.
<a href="#top">back</a></dd>
<dt><a name="keys">[2]</a></dt>
<dd>One test cycle for key generation actually consists of a constructor
call followed by one encryption resp. decryption operation, since a module
may decide to postpone the key scheduling until the direction is fixed.
The number is therefore an indicator for the encryption/decryption
performance for small chunks of data.
benchmark/benchmark_by_ebytes.html view on Meta::CPAN
<td class="other">1536.95</td>
<td class="other">96.06</td>
</tr>
</tbody>
</table>
<hr />
<p>
Remarks:<br />
<dl>
<dt><a name="lang">[1]</a></dt>
<dd>Some modules, like Crypt::DES_EEE3 or Crypt::DES_EDE3 are actually
pure Perl modules but are implemented as a wrapper around XS modules.
These are still listed here as implemented in C.
<a href="#top">back</a></dd>
<dt><a name="keys">[2]</a></dt>
<dd>One test cycle for key generation actually consists of a constructor
call followed by one encryption resp. decryption operation, since a module
may decide to postpone the key scheduling until the direction is fixed.
The number is therefore an indicator for the encryption/decryption
performance for small chunks of data.
benchmark/benchmark_by_ekeys.html view on Meta::CPAN
<td class="other">14591.86</td>
<td class="other">1823.98</td>
</tr>
</tbody>
</table>
<hr />
<p>
Remarks:<br />
<dl>
<dt><a name="lang">[1]</a></dt>
<dd>Some modules, like Crypt::DES_EEE3 or Crypt::DES_EDE3 are actually
pure Perl modules but are implemented as a wrapper around XS modules.
These are still listed here as implemented in C.
<a href="#top">back</a></dd>
<dt><a name="keys">[2]</a></dt>
<dd>One test cycle for key generation actually consists of a constructor
call followed by one encryption resp. decryption operation, since a module
may decide to postpone the key scheduling until the direction is fixed.
The number is therefore an indicator for the encryption/decryption
performance for small chunks of data.
benchmark/benchmark_by_keysize.html view on Meta::CPAN
<td class="other">107680.75</td>
<td class="other">13460.09</td>
</tr>
</tbody>
</table>
<hr />
<p>
Remarks:<br />
<dl>
<dt><a name="lang">[1]</a></dt>
<dd>Some modules, like Crypt::DES_EEE3 or Crypt::DES_EDE3 are actually
pure Perl modules but are implemented as a wrapper around XS modules.
These are still listed here as implemented in C.
<a href="#top">back</a></dd>
<dt><a name="keys">[2]</a></dt>
<dd>One test cycle for key generation actually consists of a constructor
call followed by one encryption resp. decryption operation, since a module
may decide to postpone the key scheduling until the direction is fixed.
The number is therefore an indicator for the encryption/decryption
performance for small chunks of data.