I've been populating a cms postgres server, and the data population is much slower now than before. With around 5,000 published articles so far, creating and publishing each additional article is taking around 5 minutes. Previously, the slowest performance I saw populating on a heavily used postgres db was around at most 1 minute/article. The biggest problem seems to be doing operations like update object_context set context_id = 7149 where object_context.object_id = 15004 After turning on stats gathering for postgres, I see lots of operations like these during population, and they each take up to around 12 seconds to complete. I think the culprit is the object_context_dnm_trg trigger on object_context. I am currently populating an oracle server as well with statspack enabled, but it's too early to know yet if oracle has this problem too.
just an update on oracle performance for population with the triggers. Creating and publishing an article on oracle took at most around 3 seconds at the same changelist that postgres is taking around 5 minutes.
p4 # 39541 should improve performance on pg
Now, populating articles is going at a rate of about 50 seconds/article. This is a big improvement but still lags Oracle by quite a bit.
Closing old tickets