Thread

  1. PostgreSQL and local HDD

    Jason Long <hack3rcon@yahoo.com> — 2023-08-15T07:23:42Z

    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.
    
    Does the database have to be on a storage like EMC or QNAP?
    
    Does PostgreSQL have an option to increase speed?
    
    
    Thank you.
    
    
    
    
  2. Re: PostgreSQL and local HDD

    Olivier Gautherot <ogautherot@gautherot.net> — 2023-08-15T09:24:20Z

    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
    
  3. Re: PostgreSQL and local HDD

    Ron <ronljohnsonjr@gmail.com> — 2023-08-16T03:39:25Z

    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.
  4. Re: PostgreSQL and local HDD

    Ron <ronljohnsonjr@gmail.com> — 2023-08-16T03:40:40Z

    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.
    
    
    
    
  5. Re: PostgreSQL and local HDD

    Olivier Gautherot <ogautherot@gautherot.net> — 2023-08-16T04:48:17Z

    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
    
    >
    >
    
  6. Re: PostgreSQL and local HDD

    Ron <ronljohnsonjr@gmail.com> — 2023-08-16T04:54:35Z

    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.
  7. Re: PostgreSQL and local HDD

    Olivier Gautherot <ogautherot@gautherot.net> — 2023-08-16T06:12:09Z

    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.
    
    >
    
  8. Re: PostgreSQL and local HDD

    Andreas Joseph Krogh <andreas@visena.com> — 2023-08-16T08:40:29Z

    
    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>
     <https://www.visena.com>
    
  9. Re: PostgreSQL and local HDD

    Ron <ronljohnsonjr@gmail.com> — 2023-08-16T14:25:15Z

    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.