improve graph operation performance (rebased onto metadata)#4380
improve graph operation performance (rebased onto metadata)#4380joshmoore wants to merge 2 commits intoome:metadatafrom
Conversation
|
--rebased-from #4378 |
|
Watching stack traces (very unscientifically): Count 1: Count 7: Count 4: Count 4: Count 9: Count 17: But then I hit an OOM: I recently lowered the memory on this machine from 24 GB to 16 GB so this isn't necessarily strictly a problem with this PR, but perhaps worth looking into further. |
|
In the expected case that the same data's being deleted by only one |
|
Stopping the experiment at 4 hours with 24 GB since the server is suffering: |
|
I wonder if there's something horribly inefficient about Hibernate's |
|
Well, this is a puzzle. Using this PR on a screen with over 4,000 images and over 5,000 comments (each comment will exercise the subclass code) I'm finding that this PR offers over 40% improvement in time. It would therefore be odd if the memory usage were much worse, as I'd expect that to slow things down. However, it looks like I misread the Javadocs at the last minute before my break and I don't even need the extra synchronization, so I'll remove that, then maybe we can try again for a bit more comparative testing? |
|
@mtbc : my memory issues could well be simply the size of what I was attempting since it was a screen with hundreds of plates each with hundreds of images. |
|
I don't know at what frequency redeployments tend to needed but certainly feel free to exclude and unexclude #4400 as assists insuring it's not deleterious; it's not blocking any other work at the moment. |
This is the same as gh-4378 but rebased onto metadata.
With thanks to @joshmoore, adjust how graph traversal uses Hibernate to determine the exact class of model objects. Testing is by CI.
--no-rebase