I've seen ethernet wiring and switches slowly start to fail giving flaky responses and delays. Is it possible to change a new switch and ethernet cables and see if it still happens. Ethernet wires can get crimped or be effected by temperature and switches eventually fail when they get really old. I would try that first since it is simple and inexpensive to try.
New switch was installed, and cables swapped for extended period with no change to the issue.
With everything we have done I can only see the issue being something internal to the problem Macs- that perform perfectly otherwise. Copying a 4Gb file across the same network points does not exhibit the same issue!
Performing a search returns a list view of the images with thumbnails, tags and usage data.
This is very fast on some computers, but tediously slow on others. For example, on 1 MacBook Pro a search returning 58 images with be displayed almost instantaneously, but the same search on a PowerMac (on the same switch, same OS, more RAM, FM cache same) will take minutes. The delay appears to be rendering the thumbnails.
The thumbnail rendering is the problem. I suggest that you generate a low-res thumbnail which is displayed at 100% on the list view. v12 has new tools which will allow you to reduce an image size.
if this were so why would performance change over 30 mins, with the same search and results? And why only on some computers?
I'm presuming that different computers have different graphics cards. At a Filemaker meeting we were told that all the cpu effort is put into the image resizing. If you store an image and your container field has to resize it for display that is a relatively complex and cpu-intensive task. If you put that field onto a list view then you have to run the task for every record. Displaying the image does not need as much cpu time. So, displaying images at 100% is faster.
That's good to know Malcolm, will check that out, but given that the results can be instantaneous under some circumstances and very slow at others - from about a second to about 3 minutes - on the same computer with caching eliminated as a possible factorthen I suspect it will not be the cause, but I will check
Thanks very much
Also check out the available disk space on machines. A machine running low on disk space will generate more FM-to-FMS traffic and will be significantly slower.
Also look into the free memory. You mentioned the slow machine has more RAM but OSX has to page-out a lot then that is going to be slow things down too.
only 503Gb free on the disk!
At least 8Gb RAM, FileMaker the only application running at time of testing so free memory not an isue - confirmed with Activity Monitor