on 12-10-2013 10:24 AM
According your screenshot they are waiting for tasks - background tasks, which where scheduled using transaction SM36. You can monitor batch jobs using transaction SM37.
Background workprocesses do have other (higher) limits on the maximum memory allocation per session and do have no limit in session runtime (rdisp/max_wprun_time) compared to dialog work processes.
When analyzing the memory consumption you have to take into account, that for an idle work process the most memory the have allocated is shared memory (shared with other work processes).
The typical private memory consumption per work process is between 150-200 MB, The rest is shared memory.
If a task is running in a work process you can have a look at its session-memory-consumption by double-clicking on the wp in SM50).
kind regards
Peter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Peter.
Tell me, how it is linked tasks in the database sybmgmtdb and standart jobs that can be seen in the transaction sm36(standart jobs)? I ask because at the same time, I was overwhelmed in the database sybmgmtdb(logsegment) and everything stopped in anticipation of the release of space in logsegment of sybbmgmtdb.
Hi,
well,
> and they use all the RAM.
it is always helpful to describe your observation as exact as possible.
When talking about RAM and a process, I will normally assume that you are talking about the memory resources the process is directly allocating.
>I was overwhelmed in the database sybmgmtdb(logsegment)
it looks like you are looking for database resources probably allocated by the transactions running in the batch work processes. I am not very familiar with non-Oracle database environment, but I assume that your database is sybase ASE and that the logsegment is a database resource which is storing temporary stuff which is necessary to either perform a rollback of a transaction or stores changes to the database which is needed at later point in time recovery.
Reports running in BTC workprocesses are typically designed to run a work load which does a lot of changes on the database. Hence they require sufficient sized database resources.
kind regards
Peter
Thanks for the information. But here I just can not understand, in the screenshot that the title discussion highlighted background tasks, if for any of them klinknut twice, it does not have any information. It is unclear what kind of process, who started when and what he expects? How to deal with it, where can I find information? See screenshot.
the screenshot shows the output of a double click in SM50?
In SM50 you see the current situation - the WP 15 type BTC (background programs) is waiting.
It is started, but idle, waiting for jobs to execute.
The Job Scheduler itself is automatically running in a Dialog WP. If he detects that a job defined in SM36 has to be started he will ask the dispatcher to start the job on a BTC work process in the system.
regards
Peter
hi Step,
Please have a look at this sap help. It might clear your concept regarding Background WP.
Background Work Processes Explained
Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.