From: | Scott Mead <scottm(at)openscg(dot)com> |
---|---|
To: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Re: Causeless CPU load waves in backend, on windows, 9.5.5 (EDB binary). |
Date: | 2017-02-14 00:00:55 |
Message-ID: | CAKq0gvJ03s1_G133te0OusEanoa81OrPFfd1dpVpjm-nqzaF_g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Feb 13, 2017 at 5:10 PM, Thomas Kellerer <spam_eater(at)gmx(dot)net> wrote:
> Nikolai Zhubr schrieb am 13.02.2017 um 23:03:
>
>> Maybe I should have been more specific.
>> What I need is debugging/profiling pure communication side of server
>> operation, implying huge lots of requests and replies going over the
>> wire to and from the server within some continued (valid) session,
>> but so that the server is not actually doing anything above that (no
>> sql, no locking, no synchronizing, zero usefull activity, just
>> pumping network I/O)
>>
>
My personal favorite is 'select 1'
I know you're not looking for SQL, but, you gotta start somewhere...
>
>>
> If you are willing to drop the "no sql" requirement you could use
> something like
>
> select rpad('*', 100000000, '*');
>
> this will send a lot of data over the wire, the SQL overhead should be
> fairly small.
>
> You can send more data if you combine that with e.g. generate_series()
>
>
>
>
>
>
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
--
--
Scott Mead
Sr. Architect
*OpenSCG <http://openscg.com>*
http://openscg.com
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2017-02-14 01:36:04 | Re: xmlelement AND timestamps. |
Previous Message | Lynn Dobbs | 2017-02-13 22:56:39 | xmlelement AND timestamps. |