cancel
Showing results for 
Search instead for 
Did you mean: 

Basis Process Allocation - Best Practices???

Former Member
0 Kudos

Good day,

I am not on the basis team at my company, but I have noticed what I believe to be some possible inefficiencies in the way our processes are allocated. We run a 4.6C system with IS-U hosting about 200 concurrent users on one application server. On this app server, I can see in SM50 there are 10 dialog processes, 3 update, 3 background and a couple others. I am just wondering if this seems normal or standard to anyone. It seems that when I submit jobs to run in the background, they are always piling up due to the fact that there are only three processes there.

Does anyone have any suggestions, or better yet, can anyone point me to any "best practices" documentation that I can pass on to my basis team?

Thanks a lot in advance!

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Thanks for the feedback...

Nope, just one app server and one DB server running on the same physical server. It seems like there are always background processes waiting (SM37) and piling up over a day, as well, we get a lot of complaints of slow dialog processes during the day when many people are logged in. I fear this single-server architecture, which I understand is quite uncommon, may be the culprit, but again, I am not the basis expert, so I appreciate the feedback so that I can pass it along to the appropriate parties...

thanks...geoff

Former Member
0 Kudos

Hi Geoff,

The best practice is, you should have atleast one dialog process free at any given time.

Now there are two issues I can see,

1. Background job waiting for a log time

2. User's are facing slow response problem

For background job problem, I would suggest distributing the jobs during night time rather then running during the day time(you can use Operation mode switch to do this). By this you can convert one background process into the dialog process to accommodate dialog users.

For slow response, there could be several reasons...

. Customized transaction

. Network problem

. Hardware bottle-neck

. Profile parameters (eg. memory related)

....

So you may ask Basis expert to drill-down the possibilities to resolve the problem.

Regards,

Pinkle

Former Member
0 Kudos

Geoff,

It sounds to me like your entire installation is residing on one server. If this is the case, then I think that having more batch work processes is not practical. Especially since you are supporting 200 users with just 10 dialog work processes. Are you sure there are not several application servers? Go to transaction sm51 and see if there are additional servers in the list.

Joe Caruso