> Correct rows are wider. One of the columns is text and one is bytea.
with the PG14 the LZ4 compression is worth checking.
via
https://www.postgresql.fastware.com/blog/what-is-the-new-lz4-toast-compression-in-postgresql-14
*"""INSERT statements with 16 clientsAnother common scenario that I t
> Server B is the new server and is way more powerful than server A:
> ...
> So after all, the CPU clock speed still counts these days!
Hi Sergio,
Maybe "powerful" + "powersave"?
as I see Sever B : Processor Base Frequency : 2.40 GHz AND
* Max Turbo Frequency : 3.90 GHz*
Could you verify t
Hi Mikhail.
Postgresql version: 15.3 (Debian 15.3-1.pgdg110+1) on x86_64-pc-linux-gnu,
> compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
> And just in case it matters, this is an experimental setup, so Postgresql
> running in Docker.
>
Are you using the official Docker Postgres image, s
>Model: 850 Evo 500 GB SATA III 6Gb/s -
please check the SSD *"DRIVE HEALTH STATUS"* and the* "S.M.A.R.T values of
specified disk" *
for example - with the "smartctl" tool ( https://www.smartmontools.org/
) ( -x "Show all information for device" )
Expected output with "Samsung SSD 850 EVO
> best filesystem to run PostgreSQL on, in Terms of Performance ...
test:PostgreSQL v10.3 + Linux 5.0 File-System Benchmarks: Btrfs vs.
EXT4 vs. F2FS vs. XFS
https://www.phoronix.com/scan.php?page=article&item=linux-50-filesystems&num=3
Imre
Stephan Schmidt ezt írta (időpont: 2019. ápr. 1
> Application as a whole is expected to give an throughput of 100k
transactions per sec.
> On this env(8core cpu, 16GB) what is the TPS that we can expect?
as a reference - maybe you can reuse/adapt the "TechEmpower Framework
Benchmarks" tests - and compare your PG9.6+hardware results.
The new T
> ... txid character varying(36) NOT NULL,
> ... WHERE txnid = 'febd139d-1b7f-4564-a004-1b3474e51756'
> There is only one index (unique index btree) on 'txnID' (i.e. transaction
ID) character varying(36). Which we are creating on each partition.
IF txnid is real UUID , then you can test the
https
> "Bulk loads ...",
As I see - There is an interesting bulkload benchmark:
"How Bulkload performance is affected by table partitioning in PostgreSQL"
by Beena Emerson (Enterprisedb, December 4, 2019 )
*SUMMARY: This article covers how benchmark tests can be used to
demonstrate the effect of
> view reading information_schema is slow in PostgreSQL 12
Hi,
What is the PG version?
IF PG < 12.3 THEN maybe related to this ?
https://www.postgresql.org/docs/release/12.3/ ( Repair performance
regression in information_schema.triggers view )
Imre
regrog ezt írta (időpont: 2020. jún. 12.,
> I expect my postgres on GPC to be at least similar to the one managed by
AWS RDS
imho:
- on Google Cloud you can test with "Cloud SQL for Postgresql" (
https://cloud.google.com/sql/docs/postgres )
- on Google Compute Engine ( VM ): you have to tune the disks ; linux ;
file system ; scheduler
*> Postgres Version : *PostgreSQL 12.2,
> ... ON ... USING btree
IMHO:
The next minor (bugix&security) release is near ( expected ~ May 13th, 2021
) https://www.postgresql.org/developer/roadmap/
so you can update your PostgreSQL to 12.7 ( + full Reindexing
recommended ! )
You can find a lot o
> Apart from the above hack of filtering out live tuples to a separate
table is there anything I could do?
This is the latest PG13.3 version?
IMHO: If not, maybe worth updating to the latest patch release, as soon
as possible
https://www.postgresql.org/docs/release/13.3/
Release date: 2021-05
is planned for this
> year.
>
> pt., 14 maj 2021 o 12:08 Imre Samu napisał(a):
>
>> > Apart from the above hack of filtering out live tuples to a separate
>> table is there anything I could do?
>>
>> This is the latest PG13.3 version?
>>
>> IM
> We use different machines, different config, and different datasets.
> ...
> PostgreSQL 12.4 (Debian 12.4-1.pgdg100+1) on x86_64-pc-linux-gnu,
compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit
Is It possible to upgrade and test with PG 12.7?
IMHO: lot of changes:
* https://www.postgresql.org/docs
Hi Daniel,
side note:
Maybe you can tune the "function" with some special query optimizer
attributes:
IMMUTABLE | STABLE | VOLATILE | PARALLEL SAFE
so in your example:
create or replace function f1(int) returns double precision as
$$
declare
begin
return 1;
end;
$$ language plpgsql
> .. optimisation flags like O3
> And please suggest ... to check on the performance difference
The Phoronix has been tested the PostgreSQL 13 with Clang 12 + GCC 11.1 On
Xeon Ice Lake
* "The CFLAGS/CXXFLAGS set throughout testing were "-O3 -march=native
-flto" *
* as would be common for HPC sy
> GCC vs Clang
related:
As I see - with LLVM/Clang 14.0 ( X86_64 -O3 ) ~12% performance increase
expected with the new optimisation ( probably adapted from gcc )
- https://twitter.com/djtodoro/status/1466808507240386560
-
https://www.phoronix.com/scan.php?page=news_item&px=LLVM-Clang-14-Hoist-L
Hi Lars,
> psql (14.1, server 12.6 (Ubuntu 12.6-0ubuntu0.20.04.1))
Maybe you can upgrade to 12.9 ( from 12.6 ) (
https://www.postgresql.org/docs/release/12.9/ )
And the next minor release = pg 12.10 is expected on February 10th, 2022
https://www.postgresql.org/developer/roadmap/
As I see - o
18 matches
Mail list logo
