Heikki Linnakangas wrote:
Disabling OpenSSL compression in the source (which
is possible since OpenSSL 1.0.0) does not give me any performance
improvement.
If it doesn't give you any performance improvement then you haven't
disabled compression. Modern CPUs can easily saturate 1 GbitE with
On Tue, Nov 8, 2011 at 12:25, Albe Laurenz laurenz.a...@wien.gv.at wrote:
I can't get oprofile to run on this RHEL6 box, it doesn't record
anything, so all I can test is total query duration.
Maybe this helps you with OProfile?
Marti Raudsepp wrote:
I can't get oprofile to run on this RHEL6 box, it doesn't record
anything, so all I can test is total query duration.
Maybe this helps you with OProfile?
http://people.planetpostgresql.org/andrew/index.php?/archives/224-The-joy-of-Vx.html
Dang, you're right, I wasn't
Marti Raudsepp wrote:
Disabling OpenSSL compression in the source (which
is possible since OpenSSL 1.0.0) does not give me any performance
improvement.
If it doesn't give you any performance improvement then you haven't
disabled compression. Modern CPUs can easily saturate 1 GbitE with
Marti Raudsepp wrote:
Disabling OpenSSL compression in the source (which
is possible since OpenSSL 1.0.0) does not give me any performance
improvement.
If it doesn't give you any performance improvement then you haven't
disabled compression. Modern CPUs can easily saturate 1 GbitE with
On 04.11.2011 10:43, Albe Laurenz wrote:
Marti Raudsepp wrote:
Disabling OpenSSL compression in the source (which
is possible since OpenSSL 1.0.0) does not give me any performance
improvement.
If it doesn't give you any performance improvement then you haven't
disabled compression. Modern
Merlin Moncure wrote:
We selected a 30MB bytea with psql connected with
-h localhost and found that it makes a huge
difference whether we have SSL encryption on or off.
Without SSL the SELECT finished in about a second,
with SSL it took over 23 seconds (measured with
\timing in psql).
On Thu, Nov 03, 2011 at 03:48:11PM +0100, Albe Laurenz wrote:
I experimented some more on a recent system (RHEL6, OpenSSL 1.0.0-fips),
and it is as you say. Disabling OpenSSL compression in the source (which
is possible since OpenSSL 1.0.0) does not give me any performance
improvement.
On Fri, Oct 28, 2011 at 14:02, Albe Laurenz laurenz.a...@wien.gv.at wrote:
Without SSL the SELECT finished in about a second,
with SSL it took over 23 seconds (measured with
\timing in psql).
When you query with psql, it requests columns in text format. Since
bytea hex-encodes its value if
Heikki Linnakangas wrote:
We selected a 30MB bytea with psql connected with
-h localhost and found that it makes a huge
difference whether we have SSL encryption on or off.
Without SSL the SELECT finished in about a second,
with SSL it took over 23 seconds (measured with
\timing in psql).
On Mon, Oct 31, 2011 at 10:34 AM, Albe Laurenz laurenz.a...@wien.gv.at wrote:
Heikki Linnakangas wrote:
We selected a 30MB bytea with psql connected with
-h localhost and found that it makes a huge
difference whether we have SSL encryption on or off.
Without SSL the SELECT finished in about
On 28.10.2011 14:02, Albe Laurenz wrote:
We selected a 30MB bytea with psql connected with
-h localhost and found that it makes a huge
difference whether we have SSL encryption on or off.
Without SSL the SELECT finished in about a second,
with SSL it took over 23 seconds (measured with
\timing
We selected a 30MB bytea with psql connected with
-h localhost and found that it makes a huge
difference whether we have SSL encryption on or off.
Without SSL the SELECT finished in about a second,
with SSL it took over 23 seconds (measured with
\timing in psql).
During that time, the CPU is 100%
13 matches
Mail list logo
