PostgreSQL and local HDD

Hi Jason

On Tue, Aug 15, 2023 at 9:23 AM Jason Long <hack3rcon@yahoo.com> wrote:

Hello,
Why is the PostgreSQL database slow when it is on the server's hard drive?
My servers are HPE ProLiant DL380p G8 and HPE ProLiant DL380 G9.

Can you be more specific in your question? Reasons for the server would be
"slow" can be many and can be addressed in many ways. So additional
information would be welcome:
- Size of the database
- Number of rows (and their number of columns, size...) in the tables
- Indices and other optimization tricks
- The query itself
- ... and other server configuration parameters

Does the database have to be on a storage like EMC or QNAP?

Faster storage can only help but I would start by discarding functional
overhead.

Does PostgreSQL have an option to increase speed?

It is usually achieved by reducing the number of rows you pull from the
disk.
Try the command EXPLAIN (
https://www.postgresql.org/docs/current/sql-explain.html ) to see where
the server is wasting time.

Thank you.

--
Olivier Gautherot

On 8/15/23 04:24, Olivier Gautherot wrote:
[snip]

Does the database have to be on a storage like EMC or QNAP?

Faster storage can only help but I would start by discarding functional
overhead.

Functional overhead?

--
Born in Arizona, moved to Babylonia.

On 8/15/23 02:23, Jason Long wrote:
[snip]

Does PostgreSQL have an option to increase speed?

Like a Turbo button?

--
Born in Arizona, moved to Babylonia.

El mié, 16 ago 2023 5:39, Ron <ronljohnsonjr@gmail.com> escribió:

On 8/15/23 04:24, Olivier Gautherot wrote:

[snip]

Does the database have to be on a storage like EMC or QNAP?

Faster storage can only help but I would start by discarding functional
overhead.

Functional overhead?

I mean inefficient design, which won't be solved by changing the storage.

--
Olivier Gautherot

On 8/15/23 23:48, Olivier Gautherot wrote:

El mié, 16 ago 2023 5:39, Ron <ronljohnsonjr@gmail.com> escribió:

On 8/15/23 04:24, Olivier Gautherot wrote:
[snip]

Does the database have to be on a storage like EMC or QNAP?

Faster storage can only help but I would start by discarding
functional overhead.

Functional overhead?

I mean inefficient design, which won't be solved by changing the storage.

Ah, the normal aspects of physical design...

--
Born in Arizona, moved to Babylonia.

El mié, 16 ago 2023 6:54, Ron <ronljohnsonjr@gmail.com> escribió:

On 8/15/23 23:48, Olivier Gautherot wrote:

El mié, 16 ago 2023 5:39, Ron <ronljohnsonjr@gmail.com> escribió:

On 8/15/23 04:24, Olivier Gautherot wrote:

[snip]

Does the database have to be on a storage like EMC or QNAP?

Faster storage can only help but I would start by discarding functional
overhead.

Functional overhead?

I mean inefficient design, which won't be solved by changing the storage.

Ah, the normal aspects of physical design...

... and considerung that the OP did not quantify what "slow" means and what
his reference/expectation is.

Let's wait for the OP to give more background.

På onsdag 16. august 2023 kl. 05:40:40, skrev Ron <ronljohnsonjr@gmail.com
<mailto:ronljohnsonjr@gmail.com>>:
On 8/15/23 02:23, Jason Long wrote:
[snip]

Does PostgreSQL have an option to increase speed?

Like a Turbo button?
It actually has that, but you'll have to sacrifice some safety.

--
Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
andreas@visena.com <mailto:andreas@visena.com>
www.visena.com <https://www.visena.com&gt;
<https://www.visena.com&gt;

On 8/16/23 03:40, Andreas Joseph Krogh wrote:

På onsdag 16. august 2023 kl. 05:40:40, skrev Ron <ronljohnsonjr@gmail.com>:

On 8/15/23 02:23, Jason Long wrote:
[snip]

Does PostgreSQL have an option to increase speed?

Like a Turbo button?

It actually has that, but you'll have to sacrifice some safety.

lol... we /never/ push /that/ turbo button.

--
Born in Arizona, moved to Babylonia.