please,
When the designers delete an item in the design module, the PDMS hang up for seconds and may be minutes.
I did a DICE check and found no structure errors in the db.
I also did reconfigure to the db but it didn't solve the problem.
So, does the db has maximum number of connections?? as all the piping and equipments are created in only one design db and about ten designers R/W in that db in the same time.
How big (in Kb) is the DB file?.... There might be a performance hit (and potentially a data risk) if the db is massive. Have you or have you considered doing a compress on the db?
This seems a reasonable size to me..... Are you sure this particular DESI db is the problem??? Do other design dbs work faster in the same MDB...structural for example?? I have a thought that there could be a problem with the CATA that feeds the geometry into design, or maybe the DICT
Maybe you should DICE all the DBs in the slow MDB... if they are ok then you cold create a new trial DESI and swap this for your suspect Equi and piping in a new test MDB.... create some test items and delete is it still slow??
But the designers feedback is in the morning when few users connect to the db, there is no problem. When the connected users increase the problem appears.
My project experience suggests user numbers are very unlikely to be the issue.... PDMS multiwrite is pretty go at handling connections. I am sure there are recommended maximums... but we have about 30-40 pipers in the same DB here and no db structure or performance issues so far.
I would be inclined to agree with Codoo.... sounds like network/infrastructure. I especially agree if ALL users including non-pipers who are not using your suspect db...are getting a perfomance hit.
There are a number of ways of testing the network speed during the day....see if it changes... You might know these but just in case....
