Open Dental Forum

Has anyone else noticed a slow response time with loading mounts for images?
We've been noticing that PDFs and standalone images load very quickly however anything in a mount (even if it contains no images) take a while to load
Has anyone else noticed this behavior?

We are on release 21.2.30

When you click on a mount in the tree at the left in the Imaging Module, right? No images on the mount, huh? I'll start looking specifically for slowness there. By "a while", I'm assuming you mean more than about 2 seconds?

hi Jordan,

Correct this is in reference to using the mount tree in the imaging module

No images in mount and I'd say its usually over 2 seconds more towards 3-4 maybe 5 at peak usage

It's instantaneous for me. My mount is an FMX that's 10,700 x 3,900 pixels. What size is your mount?

2000x1700 is the average mount size
5100x3900 is the largest

So it's not a size issue. I think it might be a database issue. There don't seem to be any indices on the mount tables, which wouldn't be noticeable until you had hundreds of mounts. We'll add indices, and then you can let us know if that's better.

Gotcha. We are testing somethings on our side to limit possibilities
The tables aren't very big yet which was the inital theory
mount has 29155 lines
mountitem has 231545 lines

A to Z is stored on another VM which we thought initially might be an issue but its a 10GB link to the core of the network and all the vms have 20GB links between eachother and the file server and since adding a new mount to an existing chart has a delay we figure its not on that side of it

I'll keep doing some testing and see what we can come up with

With 231k rows and no index, that's almost certainly the problem. Fix coming soon.

Hi Jordan,

Is there an estimated release version for a index release? We hit 272K on the mountitem table and 34K on the mount table today. Response times are getting to upwards of a minute

Looks like that fix was released on 9/21.

Gotcha we jumped to 21.2.43.0 and can confirm the indexes are showing on both tables

mount 0 PRIMARY 1 MountNum A 34501 BTREE
mount 1 PatNum 1 PatNum A 34501 BTREE


mountitem 0 PRIMARY 1 MountItemNum A 272348 BTREE
mountitem 1 MountNum 1 MountNum A 90782 BTREE

We are still noticing slowness pulling up mounts. Have the indexes been implemented for the MariaDB builds as well? We might try a database conversion to see if that helps as well

There should be no difference at all between performance of MariaDb and MySQL.

I found the problem. There's no key in the document table for MountItemNum. So it loads up the mount blazing fast, but then it takes time for it to find the documents that belong on the mount. Sorry about that. I just posted a fix, so it should be released within a few days, maybe tomorrow.