Bill, Legacy does not "hold" any pictures at all, only the paths to where you have them stored. It seems probable that what you are seeing is a simple example of the bigger a database then the longer it takes to search.
Ron Ferguson http://fergys.co.uk/ "William (Bill) R. Linhart" <wrlinh...@gmail.com> wrote: >NEXT TEST – adding JPG images ONLY to picture gallery … and removing > >As I added JPGs to the picture gallery I could see the number of >seconds it took to process each addition of a link to the gallery was >increasing. The system starting holding at 35-45% CPU utilization at >the 8th addition to the picture gallery. It seemed to be in a >permanent loop in the application. > >Therefore, it appears to be related to the number of images in the >picture gallery and not the size or format of the images. These were >all small JPG images in this test. > >When I removed #8 JPG the CPU usage returned to 0% in 12 seconds. >When I removed #7 it took 8 seconds. When I removed #6 it took 5 >seconds. The number seconds to remove an image continued to decline >(improve) as I removed the rest of the images from the picture >gallery> Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
