on 07-23-2014 10:34 AM
Hello Experts,
We have enabled Max thread per operation = AUTO in MDS.ini to use multiple cores to handle the requests. Currently we have 4 CPU for the MDM server.I could see the threads has been distributed across all 4 CPU's. Current Version used : MDM 7.1 SP09
Does MDM server always route the write request to one of the CPU whereas the read request is distributed across all available CPU's?
Just to elaborate : 4 Users logged in to Data Manager. 2 Users try to create a record (Write) and other 2 does search & match (Read)
In this case, how 2 write request and 2 read operation will be treated at server level?
Kindly confirm on this
Regards,
Antony
Hi Antony,
Only thing that can be said here is that no of threads will get automatically generated depending on the number of cores that are available.So if you 4 systems with dual core processor then number of threads will be calculated as 4*2 - 1 = 7.This will get calculated automatically when you keep Max Thread per Operation as AUTO.
I do not think we can premeditate whether a particular write operation's thread would lead to CPU1 or other,as this depends much upon concurrent operations and load on CPUs.
Decreasing the number of Data Manager usage in single LAN and resorting to better network will definitely help here.
Thanks,
Ravi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ravi,
Thanks for the response.
The overall initention is to understand if mulitple write requests(W1,W2) are send to MDS (Via Data Manager, Java API) whether the write operations are carried in sequence ?
As i understand the write operations (W1) does a exclusive repository write lock , does it mean the other write requests (W2) are kept on hold till the lock gained by W1 is released?
Currently we have multiple users logged in via portal and data manager as well. Their response time of the requests are very slow. Hence this request
Regards,
Antony
Hi Antony,
One workaround I would suggest is to get rid of multiple users trying to access server at one instance when CPU utilization is high.
To monitor this you can use CLIX Command and identify the user because of whom entire repository is locked and based on that result , request the user to log off from current search operation until following locks are cleared (X-Exclusive, S-Shared)
Alphabet “X” represents exclusive lock and this happens when lot of activities keep server busy increasing CPU Utilization. We cannot define the exact time for each lock. It depends on the number of processes and no. of users logged on to specific repositories.
Shared lock (S) is another type with which users can still perform search and use client systems. With exclusive lock, it will be difficult for users to access clients and parallel operations will be on hold until this lock is cleared.
Regards,
Mir Kasim Ali
Hi Mir,
Thanks for your response.
With your comments , "With exclusive lock, it will be difficult for users to access clients and parallel operations will be on hold until this lock is cleared" , following are conclusion of my understanding
Please confirm my above understandings
Regards,
Antony
Hi Antony,
I agree with points mentioned above about the behavior of MDS.
With regard to point 3 - It is one of deciding factors for the duration for which there will be exclusive lock on the repository.Increasing this will certainly decrease exclusive lock on repository and hence less wait time for the other write operations.
Thanks,
Ravi
why this matters to you?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.