‎2013 Feb 27 9:17 PM
Hi,
Does anyone know the performance implications of using Object Services, in particular Persistence Service and Query Manager?
We have major performance problems caused by the same table data being read repeatedly by programs, RFCs and BAPIs.
A solution has been proposed to use object services to reduce database reads but I am concerned this will be at the expense of higher CPU usage.
Thanks,
Dave
‎2013 Feb 28 8:12 AM
Hi David,
In my opinion Persistence Services give you less control over the performance. It may be easier to manage objects and store them in database, but you must trust Persistence Services implementation layer. With standard queries you control how to access database and it is possible to optimize statements. But I do not know statistics, if Persistence Services can improve performance or not, but I guess it will not.
If many programs reads repeatedly single table that is actually good as database caching will be involved and you will get results much faster than by rare queries. Maybe you can consider switching on buffering for the table?
If you are experiencing performance problems then in my opinion it is most probably because of:
- indexes not matched to queries;
- inefficient internal tables handling (unsorted tables);
- inefficient algorithms, like nested loops etc.
I would recommend to check with ST05 / SAT measurements why performance is the issue to clearly find the root cause.
Regards
Adam