OEL5 iSCSI performance improvement

Hi
I've just installed the latest OEL5 updates on one of our servers which is used for disk-to-disk backup. It was previously running kernel version 2.6.18-92.1.6.0.2.el5 from June 2008 but it is now running 2.6.18-92.1.13.0.1.el5. It uses iSCSI to mount drives on a Dell MD3000i storage array.
I've always had performance problems on this server - I could only get around 20Mbyte/sec throughput to the storage array. However the latest updates have improved this enormously - I now get over 90Mbytes/sec and the backups go like the wind.
I've looked through the changes but couldn't find anything obvious - does anyone know why I got this big performance win?
Dave

Customers generally see performance improvements when upgrading to 9iAS. How the upgrade process works is explained in the documentation at http://otn.oracle.com/docs/products/ias/index.html
null

Similar Messages

7110 iSCSI Performance is ABYSMAL

I have gold support, so I opened a case on this in July*, and Sun doesn't seem to think that their machine not performing as advertised is any big deal and appears to be sitting on their thumbs. They were able to replicate the issue back in August, but no fix has been forthcoming. I updated the firmware to 2009.09.01.0.0,1-1.2 because it was supposed to improve iSCSI performance. It actually made things slightly worse.
So here's the problem:
Let's say you have an iSCSI LUN set up on a RAIDz2 pool. Until you fill up the read cache, you can copy files from the 7110 to your Windows server at wire speed. As soon as the cache fills up (and you wish to copy a file that has not been cached), the transfer rate drops to less than 10 MB/s. (!?!?!?!?!?!)
It has nothing to do with the switch. I bypassed it with a direct connection. It's not Nagle's Algorithm. I've disabled that. It's not Windows or the particular server. This behavior persists across multiple machines and operating systems. And like I said, Sun has replicated the problem.
When the file(s) are in cache and you copy them from the 7110, the Networking tab in Task Manager shows 50%-plus utilization of the NIC. Once the cache has been filled and I try to copy a non-cached file, NIC utilization drops to 7%.
I have graphs from the analytics that show that when a file is cached and you try to copy it using Windows Explorer, network utilization (on the 7110) spikes and hard disk activity drops. There is a direct correlation. If the read cache fills up part of the way into the file copy, network activity drops and hard drive activity picks up immediately.
Here's the kicker: Per instructions from the Sun support engineer, I ran iostat -xtcn from a shell before, during, and after attempts to copy a bunch of non-cached files (via Windows Explorer). Here are the results:
Sun1# iostat -xtnc
   tty         cpu
tin tout us sy wt id
   0    0   0 7 0 92
                    extended device statistics
    r/s    w/s   kr/s   kw/s wait actv wsvc_t asvc_t %w %b device
    0.3    6.2   19.0 277.0 0.0 0.1    2.8   18.7   0   1 c0t5000C50007F9EE7Bd0
    0.3    6.2   20.2 277.0 0.0 0.1    2.6   17.3   0   1 c0t5000C5000AD6B6C7d0
192.7   16.2 1249.8   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F83226Fd0
192.3   16.2 1258.3   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F816EF7d0
192.5   16.2 1249.1   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F8188BBd0
192.4   16.2 1253.9   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F83D80Bd0
192.6   16.2 1247.3   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F85377Fd0
192.6   16.2 1247.2   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F81889Fd0
192.2   16.1 1258.7   20.0 0.3 0.9    1.4    4.5   3 15 c0t5000C5000F831B5Bd0
192.5   16.2 1250.1   20.0 0.3 0.9    1.3    4.3   2 15 c0t5000C5000F8187F7d0
192.2   16.1 1264.1   20.0 0.3 0.9    1.4    4.5   3 15 c0t5000C5000F814A23d0
    0.0    0.0    0.0    0.0 0.0 0.0    0.0    0.0   0   0 c0t5000C5000F814747d0
192.2   16.2 1258.9   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F838E47d0
192.5   16.2 1246.3   20.0 0.3 0.9    1.3    4.3   2 15 c0t5000C5000F83B94Fd0
192.3   16.2 1260.3   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F814F37d0
192.7   16.2 1247.5   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F8544F7d0
    0.0    0.0    0.0    0.0 0.0 0.0    0.0    0.0   0   0 c2t0d0
    0.0    0.0    0.0    0.0 0.0 0.0    0.0    0.0   0   0 c2t0d1
Sun1# iostat -xtnc
   tty         cpu
tin tout us sy wt id
   0    0   0 7 0 92
                    extended device statistics
    r/s    w/s   kr/s   kw/s wait actv wsvc_t asvc_t %w %b device
    0.3    6.2   19.0 277.0 0.0 0.1    2.8   18.7   0   1 c0t5000C50007F9EE7Bd0
    0.3    6.2   20.2 277.0 0.0 0.1    2.6   17.3   0   1 c0t5000C5000AD6B6C7d0
192.7   16.2 1249.8   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F83226Fd0
192.3   16.2 1258.3   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F816EF7d0
192.5   16.2 1249.0   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F8188BBd0
192.4   16.2 1253.9   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F83D80Bd0
192.6   16.2 1247.3   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F85377Fd0
192.6   16.2 1247.2   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F81889Fd0
192.2   16.1 1258.7   20.0 0.3 0.9    1.4    4.5   3 15 c0t5000C5000F831B5Bd0
192.5   16.2 1250.1   20.0 0.3 0.9    1.3    4.3   2 15 c0t5000C5000F8187F7d0
192.2   16.1 1264.0   20.0 0.3 0.9    1.4    4.5   3 15 c0t5000C5000F814A23d0
    0.0    0.0    0.0    0.0 0.0 0.0    0.0    0.0   0   0 c0t5000C5000F814747d0
192.2   16.2 1258.9   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F838E47d0
192.5   16.2 1246.3   20.0 0.3 0.9    1.3    4.3   2 15 c0t5000C5000F83B94Fd0
192.3   16.2 1260.3   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F814F37d0
192.7   16.2 1247.4   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F8544F7d0
    0.0    0.0    0.0    0.0 0.0 0.0    0.0    0.0   0   0 c2t0d0
    0.0    0.0    0.0    0.0 0.0 0.0    0.0    0.0   0   0 c2t0d1
Sun1# iostat -xtnc
   tty         cpu
tin tout us sy wt id
   0    0   0 7 0 92
                    extended device statistics
    r/s    w/s   kr/s   kw/s wait actv wsvc_t asvc_t %w %b device
    0.3    6.2   19.0 277.0 0.0 0.1    2.8   18.7   0   1 c0t5000C50007F9EE7Bd0
    0.3    6.2   20.2 277.0 0.0 0.1    2.6   17.3   0   1 c0t5000C5000AD6B6C7d0
192.7   16.2 1249.8   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F83226Fd0
192.3   16.2 1258.3   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F816EF7d0
192.5   16.2 1249.0   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F8188BBd0
192.4   16.2 1253.9   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F83D80Bd0
192.6   16.2 1247.3   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F85377Fd0
192.6   16.2 1247.2   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F81889Fd0
192.2   16.1 1258.7   20.0 0.3 0.9    1.4    4.5   3 15 c0t5000C5000F831B5Bd0
192.5   16.2 1250.1   20.0 0.3 0.9    1.3    4.3   2 15 c0t5000C5000F8187F7d0
192.2   16.1 1264.0   20.0 0.3 0.9    1.4    4.5   3 15 c0t5000C5000F814A23d0
    0.0    0.0    0.0    0.0 0.0 0.0    0.0    0.0   0   0 c0t5000C5000F814747d0
192.2   16.2 1258.9   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F838E47d0
192.5   16.2 1246.3   20.0 0.3 0.9    1.3    4.3   2 15 c0t5000C5000F83B94Fd0
192.3   16.2 1260.3   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F814F37d0
192.7   16.2 1247.4   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F8544F7d0
    0.0    0.0    0.0    0.0 0.0 0.0    0.0    0.0   0   0 c2t0d0
    0.0    0.0    0.0    0.0 0.0 0.0    0.0    0.0   0   0 c2t0d1I think it is clear from this output, as well as from the lack of rapid blinking of the LEDs on the 7110 that it isn't even trying to pull the information off the hard drives.
And get this--the support engineer was able to verify that the 7110 performs iSCSI write operations faster than reads.
So my question is this: Does anyone know if it's as simple as changing a setting, or will I have to wait for Sun to get their act together?

Thanks for that information. I'm not familiar with Solaris commands, so I just did what I was told to do. Adding the interval parameter did the trick. Thank you!
So here's some output obtained during a file transfer:
Sun1# iostat -xtnc 5
   tty         cpu
tin tout us sy wt id
   0    0   0 7 0 92
                    extended device statistics
    r/s    w/s   kr/s   kw/s wait actv wsvc_t asvc_t %w %b device
    0.3    6.2   19.1 277.3 0.0 0.1    2.8   18.7   0   1 c0t5000C50007F9EE7Bd0
    0.3    6.2   20.2 277.3 0.0 0.1    2.7   17.3   0   1 c0t5000C5000AD6B6C7d0
194.2   16.2 1260.5   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F83226Fd0
193.8   16.2 1269.0   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F816EF7d0
194.1   16.2 1259.7   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F8188BBd0
193.9   16.2 1264.6   20.0 0.3 0.9    1.3    4.5   2 15 c0t5000C5000F83D80Bd0
194.1   16.2 1257.9   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F85377Fd0
194.2   16.2 1257.8   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F81889Fd0
193.7   16.2 1269.4   20.0 0.3 0.9    1.4    4.5   3 15 c0t5000C5000F831B5Bd0
194.0   16.2 1260.8   20.0 0.3 0.9    1.3    4.3   2 15 c0t5000C5000F8187F7d0
193.7   16.2 1274.9   20.0 0.3 0.9    1.4    4.5   3 15 c0t5000C5000F814A23d0
    0.0    0.0    0.0    0.0 0.0 0.0    0.0    0.0   0   0 c0t5000C5000F814747d0
193.7   16.2 1269.7   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F838E47d0
194.0   16.2 1257.0   20.0 0.3 0.9    1.3    4.3   2 15 c0t5000C5000F83B94Fd0
193.8   16.2 1271.1   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F814F37d0
194.3   16.2 1258.1   20.0 0.3 0.9    1.3    4.4   2 15 c0t5000C5000F8544F7d0
    0.0    0.0    0.0    0.0 0.0 0.0    0.0    0.0   0   0 c2t0d0
    0.0    0.0    0.0    0.0 0.0 0.0    0.0    0.0   0   0 c2t0d1
   tty         cpu
tin tout us sy wt id
   0 336   0 12 0 88
                    extended device statistics
    r/s    w/s   kr/s   kw/s wait actv wsvc_t asvc_t %w %b device
    0.0   29.5    0.0 1863.2 0.1 0.4    2.2   14.8   1   5 c0t5000C50007F9EE7Bd0
    0.0   29.1    0.0 1863.2 0.0 0.4    0.4   13.8   0   5 c0t5000C5000AD6B6C7d0
477.7    1.0 631.7    9.5 1.1 0.6    2.4    1.3 48 60 c0t5000C5000F83226Fd0
483.1    1.0 669.9    9.5 0.0 0.9    0.0    1.8   0 36 c0t5000C5000F816EF7d0
478.3    1.0 704.2    9.4 0.0 0.9    0.0    1.8   0 35 c0t5000C5000F8188BBd0
484.5    1.0 678.8    9.6 0.0 0.8    0.0    1.7   0 35 c0t5000C5000F83D80Bd0
485.3    1.0 683.3    9.6 0.0 0.8    0.0    1.7   0 35 c0t5000C5000F85377Fd0
483.9    1.0 623.8    9.5 0.0 0.8    0.0    1.7   0 35 c0t5000C5000F81889Fd0
480.1    1.0 650.3    9.5 0.0 0.9    0.0    1.9   0 37 c0t5000C5000F831B5Bd0
484.3    1.0 709.0    9.5 0.0 0.9    0.0    1.8   0 35 c0t5000C5000F8187F7d0
480.9    1.0 665.2    9.5 0.0 0.9    0.0    1.9   0 37 c0t5000C5000F814A23d0
    0.0    0.0    0.0    0.0 0.0 0.0    0.0    0.0   0   0 c0t5000C5000F814747d0
484.9    1.0 651.6    9.5 0.0 0.9    0.0    1.9   0 37 c0t5000C5000F838E47d0
483.5    1.0 718.7    9.6 0.0 0.9    0.0    1.9   0 38 c0t5000C5000F83B94Fd0
485.5    1.0 668.4    9.5 0.0 0.8    0.0    1.7   0 35 c0t5000C5000F814F37d0
482.9    1.0 675.4    9.4 0.0 0.8    0.0    1.7   0 35 c0t5000C5000F8544F7d0
    0.0    0.0    0.0    0.0 0.0 0.0    0.0    0.0   0   0 c2t0d0
    0.0    0.0    0.0    0.0 0.0 0.0    0.0    0.0   0   0 c2t0d1
   tty         cpu
tin tout us sy wt id
   0 336   0 8 0 91
                    extended device statistics
    r/s    w/s   kr/s   kw/s wait actv wsvc_t asvc_t %w %b device
    0.2    0.0    0.2    0.0 0.0 0.0    0.0    0.1   0   0 c0t5000C50007F9EE7Bd0
    0.2    0.0    0.1    0.0 0.0 0.0    0.0    0.3   0   0 c0t5000C5000AD6B6C7d0
643.7    1.2 967.9    3.5 1.2 0.7    1.8    1.0 50 67 c0t5000C5000F83226Fd0
662.1    1.2 946.4    3.3 0.0 1.1    0.0    1.6   0 43 c0t5000C5000F816EF7d0
667.1    1.2 943.2    3.6 0.0 1.1    0.0    1.6   0 43 c0t5000C5000F8188BBd0
670.5    1.2 952.7    3.6 0.0 1.0    0.0    1.5   0 41 c0t5000C5000F83D80Bd0
673.3    1.2 938.0    3.6 0.0 1.0    0.0    1.5   0 40 c0t5000C5000F85377Fd0
666.5    1.2 945.6    3.5 0.0 0.9    0.0    1.4   0 39 c0t5000C5000F81889Fd0
667.1    1.2 948.3    3.3 0.0 1.0    0.0    1.5   0 41 c0t5000C5000F831B5Bd0
671.5    1.2 945.1    3.5 0.0 1.0    0.0    1.5   0 40 c0t5000C5000F8187F7d0
671.1    1.2 964.0    3.4 0.0 1.1    0.0    1.6   0 42 c0t5000C5000F814A23d0
    0.0    0.0    0.0    0.0 0.0 0.0    0.0    0.0   0   0 c0t5000C5000F814747d0
669.7    1.2 973.7    3.2 0.0 1.0    0.0    1.6   0 42 c0t5000C5000F838E47d0
668.9    1.2 926.0    3.6 0.0 1.0    0.0    1.5   0 40 c0t5000C5000F83B94Fd0
671.3    1.2 928.2    3.3 0.0 1.1    0.0    1.6   0 42 c0t5000C5000F814F37d0
673.3    1.2 932.2    3.6 0.0 1.0    0.0    1.5   0 40 c0t5000C5000F8544F7d0
    0.0    0.0    0.0    0.0 0.0 0.0    0.0    0.0   0   0 c2t0d0
    0.0    0.0    0.0    0.0 0.0 0.0    0.0    0.0   0   0 c2t0d1
   tty         cpu
tin tout us sy wt id
   0 336   0 10 0 90
                    extended device statistics
    r/s    w/s   kr/s   kw/s wait actv wsvc_t asvc_t %w %b device
    0.0    0.0    0.0    0.0 0.0 0.0    0.0    0.0   0   0 c0t5000C50007F9EE7Bd0
    0.0    0.0    0.0    0.0 0.0 0.0    0.0    0.0   0   0 c0t5000C5000AD6B6C7d0
532.9    0.8 752.0    7.1 1.1 0.6    2.1    1.1 48 61 c0t5000C5000F83226Fd0
550.7    0.8 762.7    7.2 0.0 0.9    0.0    1.7   0 35 c0t5000C5000F816EF7d0
548.3    0.8 776.3    7.2 0.0 0.9    0.0    1.7   0 37 c0t5000C5000F8188BBd0
551.1    0.8 812.9    7.2 0.0 0.9    0.0    1.7   0 37 c0t5000C5000F83D80Bd0
551.1    0.8 752.3    7.2 0.0 0.9    0.0    1.6   0 36 c0t5000C5000F85377Fd0
548.1    0.8 755.3    7.1 0.0 0.9    0.0    1.6   0 34 c0t5000C5000F81889Fd0
544.5    0.8 800.4    7.2 0.0 1.0    0.0    1.8   0 38 c0t5000C5000F831B5Bd0
553.9    0.8 736.8    7.2 0.0 0.9    0.0    1.6   0 36 c0t5000C5000F8187F7d0
552.3    0.8 797.5    7.2 0.0 0.9    0.0    1.6   0 36 c0t5000C5000F814A23d0
    0.0    0.0    0.0    0.0 0.0 0.0    0.0    0.0   0   0 c0t5000C5000F814747d0
549.1    0.8 788.2    7.2 0.0 0.9    0.0    1.7   0 37 c0t5000C5000F838E47d0
548.5    0.8 787.3    7.1 0.0 0.9    0.0    1.7   0 36 c0t5000C5000F83B94Fd0
552.3    0.8 756.7    7.2 0.0 0.9    0.0    1.7   0 36 c0t5000C5000F814F37d0
545.3    0.8 795.7    7.1 0.0 0.9    0.0    1.7   0 37 c0t5000C5000F8544F7d0
    0.0    0.0    0.0    0.0 0.0 0.0    0.0    0.0   0   0 c2t0d0
    0.0    0.0    0.0    0.0 0.0 0.0    0.0    0.0   0   0 c2t0d1I don't know how to interpret this, so any help would be greatly appreciated.
Thanks!

Tabular Model Performance Improvements

Hi !
We have a bulitv tabular model inline which has a fact table and 2 dimension tables .The performance of SSRS report is very slow and we have bottle neck in deciding SSRS as reporting tool.
Can you help us on performance improvements with Tabular Inline
Regards,

Hi Bhadri,
As Sorna said, it hard to give you the detail tips to improve the tabular model performance according the limited information. Here are some useful link about performance Tuning of Tabular Models in SQL Server 2012 Analysis Services, please refer to the
link below.
http://msdn.microsoft.com/en-us/library/dn393915.aspx
If this is not what you want, please elaborate the detail information, so that we can make further analysis.
Regards,
Charlie Liao
TechNet Community Support

DS 5.2 P4 performance improvement

We have +/- 300,000 users that regularly authenticate using our DS. The user ou is divided in ou=internal (20,000 ids) and ou=external (280,000) uids. Approximately 85-90% percent of the traffic happens on the internal ou. The question is: Could I get any performance improvement by separating the internal branch into its own suffix/database? Would running two databases adversely affect the performance instead? We see performance impacts when big searches are performed on the ou=external branch. Would the separation isolate the issue, or those searches will most likely affect the DS as a whole?
Thanks for your help!
Enrique.

Thank you for the info. Are u a Sun guy - do you work
for sun?Yes I am. I'm the Architect for Directory Server Enterprise Edition 6.0. Previously I worked on all DS 5 releases (mostly on Replication).
You are getting the Dukes!Thanks.
Ludovic.

Performance improvement in a function module

Hi All,
I am using SAP 6.0 version. I have a function module to retrive the PO's . for just 10,000 records its taking long time.
Can any one sugguest the ways to improve the performance.
Thanks in advance.

Moderator message - Welcome to SCN.
But
Moderator message - Please see Please Read before Posting in the Performance and Tuning Forum before posting
Just 10,000 records? The first rule in performance improvement is to reduce the amount of selected data. If you cannot do that, it's going to take time.
I wouldn't bother with a BAPI for so many records. Write some custom code to get only the data you need.
Tob

Pls help me to modify the query for performance improvement

Hi,
I have the below initialization
DECLARE @Active bit =1 ;
Declare @id int
SELECT @Active=CASE WHEN id=@id and [Rank] ='Good' then 0 else 1 END FROM dbo.Students
I have to change this query in such a way that the conditions id=@id and [Rank] ='Good' should go to the where condition of the query. In that case, how can i use Case statement to retrieve 1 or 0? Can you please help me to modify this initialization?

I dont understand your query...May be below? or provide us sample data and your output...
SELECT * FROM dbo.students
where @Active=CASE
WHEN id=@id and rank ='Good' then 0 else 1 END
But, I doubt you will have performance improvement here?
Do you have index on id?
If you are looking for getting the data for @ID with rank ='Good' then use the below:Make sure, you have index on id,rank combination.
SELECT * FROM dbo.students
where id=@id
and rank ='Good'

Performance improvement in OBIEE 11.1.1.5

Hi all,
In OBIEE 11.1.1.5 reports takes long time to load , Kindly provide me some performance improvement guides.
Thanks,
Haree.

Hi Haree,
Steps to improve the performance.
1. implement caching mechanism
2. use aggregates
3. use aggregate navigation
4. limit the number of initialisation blocks
5. turn off logging
6. carry out calculations in database
7. use materialized views if possible
8. use database hints
9. alter the NQSONFIG.ini parameters
Note:calculate all the aggregates in the Repository it self and Create a Fast Refresh for MV(Materialized views).
and you can also do one thing you can schedule an IBOT to run the report every 1 hour or some thing so that the report data will be cached and when the user runs the report the BI Server extracts the data from Cache
This is the latest version for OBIEE11g.
http://blogs.oracle.com/pa/resource/Oracle_OBIEE_Tuning_Guide.pdf
Report level:
1. Enable cache -- change nqsconfig instead of NO change to YES.
2. GO--> Physical layer --> right click table--> properties --> check cacheable.
3. Try to implement Aggregate mechanism.
4.Create Index/Partition in Database level.
There are multiple other ways to fine tune reports from OBIEE side itself:
1) You can check for your measures granularity in reports and have level base measures created in RPD using OBIEE utility.
http://www.rittmanmead.com/2007/10/using-the-obiee-aggregate-persistence-wizard/
This will pick your aggr tables and not detailed tables.
2) You can use Caching Seeding options. Using ibot or Using NQCMD command utility
http://www.artofbi.com/index.php/2010/03/obiee-ibots-obi-caching-strategy-with-seeding-cache/
http://satyaobieesolutions.blogspot.in/2012/07/different-to-manage-cache-in-obiee-one.html
OR
http://hiteshbiblog.blogspot.com/2010/08/obiee-schedule-purge-and-re-build-of.html
Using one of the above 2 methods, you can fine tune your reports and reduce the query time.
Also, on a safer side, just take the physical SQL from log and run it directly on DB to see the time taken and check for the explain plan with the help of a DBA.
Hope this help's
Thanks,
Satya
Edited by: Satya Ranki Reddy on Aug 12, 2012 7:39 PM
Edited by: Satya Ranki Reddy on Aug 12, 2012 8:12 PM
Edited by: Satya Ranki Reddy on Aug 12, 2012 8:20 PM

MV Refresh Performance Improvements in 11g

Hi there,
the 11g new features guide, says in section "1.4.1.8 Refresh Performance Improvements":
"Refresh operations on materialized views are now faster with the following improvements:
1. Refresh statement combinations (merge and delete)
2. Removal of unnecessary refresh hint
3. Index creation for UNION ALL MV
4. PCT refresh possible for UNION ALL MV
While I understand (3.) and (4.) I don't quite understand (1.) and (2.). Has there been a change in the internal implementation of the refresh (from a single MERGE statement)? If yes, then which? Is there a Note or something in the knowledge base, about these enhancements in 11g? I couldn't find any.
Considerations are necessary for migration decision to 11g or not...
Thanks in advance.

I am not quit sure, what you mean. You mean perhaps, that the MVlogs work correctly when you perform MERGE stmts with DELETE on the detail tables of the MV?
And were are the performance improvement? What is the refresh hint?
Though I am using MVs and MVlogs at the moment, our app performs deletes and inserts in the background (no merges). The MVlog-based fast refresh scales very very bad, which means, that the performance drops very quickly, with growing changed data set.

Why GN_INVOICE_CREATE has no performance improvement even in HANA landscape?

Hi All,
We have a pricing update program which is used to update the price for a Material Customer combination(CMC).This update is done using the FM 'GN_INVOICE_CREATE'.
The logic is designed to loop on customers, wherein this FM will be called passing all the materials valid for that customer.
This process is taking days(Approx 5 days) to get executed and updated for CMC of 100 million records.
Hence we are planning to move towards HANA for better improvement in performance.
We designed the same programs in the HANA landscape and executed it in both systems for 1 customer and 1000 material combination.
Unfortunately, both the systems gave same runtimes around 27 seconds for execution.
This is very disappointing thinking the performance improvement we should have on HANA landscape.
Could anyone throw light on any areas where we are missing out and why no performance improvement was obtained ?
Also is there any configuration related changes to be done on HANA landscape for better performance.?
The details regarding both the systems are as below.
Suite on HANA:
SAP_BASIS : 740
SAP_APPL : 617
ECC
SAP_BASIS : 731
SAP_APPL : 606
Also see the below screenshots of the system details.
HANA:
ECC:
Thanks & regards,
Naseem

Hi,
just to fill in on Lars' already exhaustive comments:
Migrating to HANA gives you lots of options to replace your own functionality (custom ABAP code) wuth HANA artifacts - views or SQLscript procedures. This is where you can really gain on performance. Expecting ABAP code to automatically run faster on HANA may be unrealistic, since it depends on the functionality of the code and how well it "translates" to a HANA environment. The key to really minimize run time is to replace DB calls with specific HANA views or procedures, then call these from your code.
I wrote a blog on this; you might find it useful as a general introduction:
A practical example of ABAP on HANA optimization
When it comes to SAP standard code, like your mentioned FM, it is true that SAP is migrating some of this functionality to HANA-optimized versions, but this doesn't mean everything will be optimized in one go. This particular FM is probably not among those being initially selected for "HANAification", so you basically have to either create your own functionality (which might not be advisable due to the fact that this might violate data integrity) or just be patient.
But again, the beauty of HANA lies in the brand new options for developers to utilize the new ways of pushing code down to the DB server. Check out the recommendations from Lars and you'll find yourself embarking on a new and exciting journey!
Also - as a good starting point - check out the HANA developer course on open.sap.com.
Regards,
Trond

Will there performance improvement over separate tables vs single table with multiple partitions?

Will there performance improvement over separate tables vs single table with multiple partitions? Is advisable to have separate tables than having a single big table with partitions? Can we expect same performance having single big table with partitions? What is the recommendation approach in HANA?

Suren,
first off a friendly reminder: SCN is a public forum and for you as an SAP employee there are multiple internal forums/communities/JAM groups available. You may want to consider this.
Concerning your question:
You didn't tell us what you want to do with your table or your set of tables.
As tables are not only storage units but usually bear semantics - read: if data is stored in one table it means something else than the same data in a different table - partitioned tables cannot simply be substituted by multiple tables.
Looked at it on a storage technology level, table partitions are practically the same as tables. Each partition has got its own delta store & can be loaded and displaced to/from memory independent from the others.
Generally speaking there shouldn't be too many performance differences between a partitioned table and multiple tables.
However, when dealing with partitioned tables, the additional step of determining the partition to work on is always required. If computing the result of the partitioning function takes a major share in your total runtime (which is unlikely) then partitioned tables could have a negative performance impact.
Having said this: as with all performance related questions, to get a conclusive answer you need to measure the times required for both alternatives.
- Lars

DMA Performance Improvements for TIO-based Devices

Hello!
DMA Performance Improvements for TIO-based Devices
http://digital.ni.com/public.nsf/websearch/1B64310FAE9007C086256A1D006D9BBF
Can I apply the procedure to NI-DAQmx 9? These ini-files dont seem to exist anymore in the newer version.
Best, Viktor

Hi Viktor,
this page is 7 years old and doesn't apply to the DAQmx.
Regards, Stephan

Performance improve using TEZ/HIVE

Hi,
I’m newbie in HDInsight. Sorry for asking simple Questions. I have queries around performance improvement of my HIVE query on File data of 90 GB (15 GB * 6).
We have enabled execution engine has TEZ, I heard the AVRO format improves the speed of execution, Is AVRO SERDE enabled TEZ Queries or do I need upload *.jar files to WASB. I’m using latest version. Any sample Query.
In TEZ, Will ORC Column Format and Avro compression can work together, when we set ORC compression level on hive has
Snappy and LZO ?. Is there any Limitation of Number of columns for ORC tables.
Is there any best compression technique to upload data file to Blob, I mean compress and upload. I used *.gz, which compressed by 1/4<sup>th</sup> of File Size and upload to Blob, but problem *.gz is not split able and it will always
uses less (single ) Mapper or should I use Avro with Snappy Compression . Is the Microsoft Avro Library performs snappy Compression or is there any compress which can be split and compress.
If data structure for file change over time , will there be necessity of reloading older data?. Can existing query works without change in code.
It has been said that TEZ has Real Time Reporting capability , but when I Query 90 GB file (It includes Group By, order by clauses) is taking almost 8 mins of time on 20 nodes, are there any pointers to improve performance further and get the Query result
in Seconds.
Mahender

-- Tez is an execution engine, I don't think you need any additional jar file to get AVRO Serde working on Hive when Tez is used. You can used AvroSerDe, AvroContainerInputFormat & AvroContainerOutputFormat to get AVRO working when tez is
used.
-- I tried creating a table with about 220 columns, although the table was empty, I was able to query from the table, how many columns does your table hold?
CREATE EXTERNAL TABLE LargColumnTable02(t1 string,.... t220 string)
PARTITIONED BY(EventDate string) ROW FORMAT DELIMITED FIELDS TERMINATED BY ',' STORED AS ORC LOCATION '/data'
tblproperties("orc.compress"="SNAPPY");
-- You can refer
http://dennyglee.com/2013/03/12/using-avro-with-hdinsight-on-azure-at-343-industries/
Getting Avro data into Azure Blob Storage Section
-- It depends on what data has change , if you are using Hadoop, HBase etc..
-- You will have to monitor your application check node manager logs if there is any pause in execution again. It depends on what you are doing, would suggest open a Support case to investigate further.

Performance improvement from OAS 4.0.7 to 9iAS

Any performance improvement from OAS4.0.7 to 9iAS. What are the parameters to be changed to upgrade from 4.0.7 to 9iAS.
Regards,

Customers generally see performance improvements when upgrading to 9iAS. How the upgrade process works is explained in the documentation at http://otn.oracle.com/docs/products/ias/index.html
null

Performance Improvement between GDK and EDK portlets

Are there any performance improvements to be expected by migrating a portlet from using the GDK library to EDK library? Not looking at what GDK and EDK offers, more on whether we would improve the load time of a portal page if we change a portlet from GDK to EDK.....

With GDK, my pages inherit from "Plumtree.Remote.Csp.UI.Page" and under the hood, the context is created (SettingsManager) automatically. Apparently, this is not the case anymore with the EDK. Am I correct?
According to the EDK doc, I need to call "PortletContextFactory.CreatePortletContext(Request,Response)" for such purpose. Still correct?
-- Yes, correct. In the EDK, no SettingsManager is used, and the functionality is wrapped into IPortletRequest and IPortletResponse.
The other more important change is that with the GDK, the language of the current thread is automatically set to the language passed by the portal in the "Accept-Language" HTTP header. This is not the case anymore, to my knowledge, and I found out that I need to insert this:
String sLanguage = HttpContext.Current.Request.UserLanguages[0];System.Threading.Thread.CurrentThread.CurrentCulture=new System.Globalization.CultureInfo(sLanguage);
Is this correct or did I miss something?
-- You do not need to use the HttpContext object of .NET. The Plumtree EDK allows you to retrieve the language as follows: The portal language is stored in a User Pref named "strLocale". A remote portlet can read this User Pref.The only point to note is that, as with all User Prefs, you must ensure that the specific prefs are sent to the portlet in the Portlet Web Service registration.
PortletRequest.GetSettingValue(Plumtree.Remote.Portlet.SettingType.User, "strTimeZone")

Performance Improvements (Follow-Up from P2P)

Business One response time has great impact on customer satisfaction. We want to further invest in this area and therefore asking for your feedback.
We would like to further improve performance in areas that are important for a typical customer profile. With this goal in mind we look for you advice on specific performance bottle neck that you recommend us to focus on.
This thread is continuation from 'Performance Improvements' <a href="http://p2p.sap.com/businessoneforum?type=join&login=1&uid=41FB661A76CED536C825C4E2B6FF4397&cid=91&go=z37225">discussion</a> in P2P SAP Business One Forum (Product Development Collaboration). Previous discussion on P2P is summarized in the attached file.

Peter,
We are also having intermittent performance issues with SBO. Our main usage is with A/R invoice whereby we have approx 10 x users processing A/R invoices in remote locations (WAN, via 2 x Citrix Servers - both Dual Xeon 3.06Ghz with 4gb DDR RAM). We process some +9,000 A/R invocies per month with a total of approx 250,000 rows per month. We have recently upgraded from SBO2004A to SBO2005 SP01 PL18 and have noted a huge backwards step in system response time (performance). Copied below are some recent times recored:
We also have local users (connected directly to SBO - not via Citrix) and the performce is good.
Look fowards to your feedback as to how we can improve on this current situation which is costing us valuable time (and money)
P.s Can you also send me a copy of the Performance Improvement Discussion. I am unable to download the file from the link in the forum.
Thanks Ron
[email protected]
"12.29 seconds just to open an A/R Invoice (from when you click on A/R Invoice button to when it actually opens)
43.28 seconds from when you click the final add on a credit to when the credit actually processes
18.57 seconds from when you click the final add on an invoice to when the invoice actually processes
58.08 seconds from when you click the first add on an invoice to when the invoice actually processes"
When you multiply these times out by +9,000 A/R invocies. The problem is quite serious!

OEL5 iSCSI performance improvement

Similar Messages

Maybe you are looking for