![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
We have a 10g database on Solaris 10 that is having some serious performance issues. *The same database restored onto a Windows machine performs fine. I'm not sure if the Solaris/Windows thing makes a difference at all, but I'm curious if anyone knows of anything. Some background: *We discovered the issue while optimizing a query, and examining the explain plan cost of the query. *Unoptimized, this query had a cost of 256000 in 10g/Solaris. *It had a cost of 6 in 10g/ Windows. Optimized, the query had a cost of 51 in 10g/Solaris, and a cost of 4 in 10g/Windows. *So we're still seeing a pretty huge difference on this query alone, and the general performance of the Solaris DB is just very poor, despite the hardware being far superior to the Windows machine. The Solaris DB is WE8ISO8859P1 character set. *The Windows DB is WE8MSWIN1252. *Any ideas? *Other information I can provide? Thanks, Alex |
#3
| |||
| |||
|
#4
| |||
| |||
|
|
We have a 10g database on Solaris 10 that is having some serious performance issues. The same database restored onto a Windows machine performs fine. I'm not sure if the Solaris/Windows thing makes a difference at all, but I'm curious if anyone knows of anything. Some background: We discovered the issue while optimizing a query, and examining the explain plan cost of the query. Unoptimized, this query had a cost of 256000 in 10g/Solaris. It had a cost of 6 in 10g/ Windows. Optimized, the query had a cost of 51 in 10g/Solaris, and a cost of 4 in 10g/Windows. So we're still seeing a pretty huge difference on this query alone, and the general performance of the Solaris DB is just very poor, despite the hardware being far superior to the Windows machine. The Solaris DB is WE8ISO8859P1 character set. The Windows DB is WE8MSWIN1252. Any ideas? Other information I can provide? Thanks, Alex |
#5
| |||
| |||
|
|
On Fri, 19 Aug 2011 08:00:25 -0700, Alex L wrote: We have a 10g database on Solaris 10 that is having some serious performance issues. *The same database restored onto a Windows machine performs fine. I'm not sure if the Solaris/Windows thing makes a difference at all, but I'm curious if anyone knows of anything. Some background: *We discovered the issue while optimizing a query, and examining the explain plan cost of the query. *Unoptimized, this query had a cost of 256000 in 10g/Solaris. *It had a cost of 6 in 10g/ Windows. Optimized, the query had a cost of 51 in 10g/Solaris, and a cost of 4 in 10g/Windows. *So we're still seeing a pretty huge difference on this query alone, and the general performance of the Solaris DB is just very poor, despite the hardware being far superior to the Windows machine. The Solaris DB is WE8ISO8859P1 character set. *The Windows DB is WE8MSWIN1252. *Any ideas? *Other information I can provide? Thanks, Alex Is there any difference in the system statistics? What are the values in SYS.AUX_STATS$ table? These values govern the behavior of the CBO. Also, is there any significant discrepancy in the instance parameters? --http://mgogala.byethost5.com |
#6
| |||
| |||
|
|
Joel, I can gather the information you request, but it won't be today. *And to clarify, the issue is not with the query exactly, but really with an app that is universally slow in the Solaris environment, but runs perfectly acceptably in Windows and Redhat (though the Redhat environment uses AL32UTF8, which is why we are thinking this might be character set related). *We have pretty well narrowed down that the bottleneck appears to the be DB, rather than other network issues. snip Sorry for the lack of specifics, kinda new to Oracle, and I was mainly looking for directions to go in for troubleshooting and gathering more specific data. *Thanks everyone. -Alex |
#7
| |||
| |||
|
#8
| |||
| |||
|
|
Mladen, it appears that both have up to date statistics, running GATHER_STATS_JOB nightly. SYS.AUX_STATS$ are basically the same, difference CPUSPEED numbers. Solaris: SYSSTATS_INFO STATUS COMPLETED SYSSTATS_INFO DSTART 01-21-2006 05:43 SYSSTATS_INFO DSTOP 01-21-2006 05:43 SYSSTATS_INFO FLAGS 1 SYSSTATS_MAIN CPUSPEEDNW 452.169401387898 SYSSTATS_MAIN IOSEEKTIM 10 SYSSTATS_MAIN IOTFRSPEED 4096 SYSSTATS_MAIN SREADTIM SYSSTATS_MAIN MREADTIM SYSSTATS_MAIN CPUSPEED SYSSTATS_MAIN MBRC SYSSTATS_MAIN MAXTHR |
#9
| |||
| |||
|
|
10.2.0.1 is the base release of 10.2 not patched up at all. |
#10
| |||
| |||
|
|
We have a 10g database on Solaris 10 that is having some serious performance issues. *The same database restored onto a Windows machine performs fine. I'm not sure if the Solaris/Windows thing makes a difference at all, but I'm curious if anyone knows of anything. Some background: *We discovered the issue while optimizing a query, and examining the explain plan cost of the query. *Unoptimized, this query had a cost of 256000 in 10g/Solaris. *It had a cost of 6 in 10g/ Windows. Optimized, the query had a cost of 51 in 10g/Solaris, and a cost of 4 in 10g/Windows. *So we're still seeing a pretty huge difference on this query alone, and the general performance of the Solaris DB is just very poor, despite the hardware being far superior to the Windows machine. The Solaris DB is WE8ISO8859P1 character set. *The Windows DB is WE8MSWIN1252. *Any ideas? *Other information I can provide? Thanks, Alex |
![]() |
| Thread Tools | |
| Display Modes | |
| |