Обсуждение: 64 Bit / Swap Issue?
Hi Guys,
We have been running our systems on high end Redhat ES 32 Bit servers without any sort of glitch. We have now set up a 64 bit Athlon server running Redhat ES, installed the Redhat PgSQL as well as the PHP5 RPM.
I have been experiencing incredible slow performance from my server, and am at a loss for solution. Should I be moving back to a 32 bit system?
This is the reply I have from Rackspace:
“Secondly "sar" is showing that you are dipping quite a bit into your swap space. When dealing with a database server, any time that you move from RAM to swap you will see a massive performance drop, especially when dealing with as much swap as this machine has. At its peak you were hitting 70%(700M) of swap. Since PostgreSQL is unsupported I don't have any suggestions on query optimizations. However, at this point upgrading your available RAM would be one of my best suggestions.”
Does anyone have any experience on this? Most of the things I have read suggest that I move back to 32 bit but I do think it’s a step backward – that’s if this can be supported.
Regards and thanks,
James Dey
james@mygus.com
0861-11-44-03
Intl. : +27 (0) 11 704-1945
Fax : +27 (0) 11 3888-907
Mobile : +27 (0) 82-7855-102
Hi James, On Dec 5, 2005, at 12:11 AM, James Dey wrote: > “Secondly "sar" is showing that you are dipping quite a bit into > your swap space. When dealing with a database server, any time > that you move from RAM to swap you will see a massive performance > drop, especially when dealing with as much swap as this machine > has. At its peak you were hitting 70%(700M) of swap. Since > PostgreSQL is unsupported I don't have any suggestions on query > optimizations. However, at this point upgrading your available RAM > would be one of my best suggestions.” > > > > Does anyone have any experience on this? Most of the things I have > read suggest that I move back to 32 bit but I do think it’s a step > backward – that’s if this can be supported. Welcome to the list. I don't have an answer for you but I'll suggest that you might have better luck finding one on the performance list. Or even the general list. Also there are archives for all lists which might also provide some clues. John DeSoi, Ph.D. http://pgedit.com/ Power Tools for PostgreSQL
On Mon, Dec 05, 2005 at 07:11:25 +0200, James Dey <james@mygus.com> wrote: > > I have been experiencing incredible slow performance from my server, and am > at a loss for solution. Should I be moving back to a 32 bit system? I think it is unlikely that the switch to 64bit architecture is what is causing your problem. You should ask again on the performance list. You want to include some more details on hardware, such as the amount of memory and your disk set up. You should include your postgresql.conf settings as there might be something there that is causing a problem. You should state what version of postgres you are running and what OS you are using. You should include information about what else is running on that server. It is possible that something other than Postgres is using the memory. Have you looked at ps output to try to identify which processes are using lots of memory? If you have identified any slow queries, it would be helpful to see EXPLAIN ANALYSE output for them. Your problem is probably not a bad plan, but there could be an issue with a query taking up a lot of memory if you workmem limit is very high.
James Dey wrote: > --> > > Hi Guys, > > We have been running our systems on high end Redhat ES 32 Bit servers > without any sort of glitch. We have now set up a 64 bit Athlon server > running Redhat ES, installed the Redhat PgSQL as well as the PHP5 RPM. > Do the machines have a different amount of RAM? There is no reason that a 32 bit machine versus a 64bit machines should swap noticeably more unless something has changed. > /“Secondly "sar" is showing that you are dipping quite a bit into your > swap space. When dealing with a database server, any time that you > move from RAM to swap you will see a massive performance drop, > especially when dealing with as much swap as this machine has. At its > peak you were hitting 70%(700M) of swap. Since PostgreSQL is > unsupported I don't have any suggestions on query optimizations. > However, at this point upgrading your available RAM would be one of my > best suggestions.”/ > Well there response is correct but the question is why are you hitting swap. Please see my quseton above. > > Does anyone have any experience on this? Most of the things I have > read suggest that I move back to 32 bit but I do think it’s a step > backward – that’s if this can be supported. > There is no reason for you to move back to 32bit. Joshua D. Drake