We are using a test database consisting of 120,000 listings (which is around 4 GB data of disk without counting in images). Using this database we worked out all performance issues we encountered.
So, if you are still running into issues, you might be triggering a code path that we havenāt optimized yet, or your Mac is a lot slower than the ones we use. All our Macs have SSDs and at at least 16 GB of RAM.
Iām guessing that we will have to upgrade system to keep up?
Iām pretty sure Iām running 5400 rpm hard drives on both of my machines and both have 8gb of ram.
My 1300+ listing have images (12 images all).
My garage sale database is near 12 GB of data.
Maybe itās time for you guys @ilja to add images to your test database, images definitely are a game changer, I donāt sell inventory type items I used Antiques so all of my listings are very specific and unique in nature.
Thereās isnāt any getting around for me than possibly to switching software product or upgrading to a super-fast mac pc. I need to weigh my options and see whatās the most economical way to go about, I have to spend money to make money 
No GarageSale7ās fault software needs improvement periodically.
I hope that you guys release some preliminary specs on what the software needs in terms of hardware power.
Iāll see what strategy I end-up going with.
Thank you for the support.
Hello People,
I sell antiques and collectibles too so HD images are the most important feature. A medium image is about 40-50 MB. I created about 700-800 listing in one month so I supposte in 1 year I will have at least 10.000. But this is not a limit for me. At this moment I am using GTC listing with only 2 images for each one (they are small, taken with scanner), but as soon as I finish the first stock (postcard) I will start with others (just some examples, ancient books or vintage items need at least 10-15 photo each one). I know I should upgrade my mac, itās quite old and I am looking to expand RAM, but ā¦
Well, I supposte 16 will be the very best limit for me 
.
What do you mean @ilja ?
This sounds amazing, it will be my motto 
really really trueā¦
THE HD picture size is a big problem extending uploads time and CPU loads
THE RESOLUTION HAS TO BE SET IN PIXALS USING WWW.VSMEDIA.DE IMAGE SIZE APP
This IOS app reduces it to the maximum resolution that Ebay and the most users screens support.
You specify the size of the picture and it sorts it out. This reduces the size of the Image database.
Secondly you should have your own image database online at hostgator or go daddy
Even if your listing is down for a week or two your picture links stay current and you can just reload the auction
This is important as you spread the likelihood of a full data loss in the case of a computer drive failing.
If we see a spinning beach ball while using GarageSale 7, we investigate whatās locking GarageSale up and try to change the code, so the hang lockup goes away. Usually you can add some caches, use a different algorithm or throttle interface updates to make the application fasterā¦
So, if you are still seeing the beach ball a lot, you are probably doing something that we arenāt doing, are you data is very different from the data we test and develop with. Or you Mac is just slow. 
I am not a programmer but I think itās just a bit too memory for GS. I started working this morning, took that screen at about 14 p.m. , but it is constantly increasing, now it takes 1,28 GB ā¦
I will expand memory, it is in my to do list, and if I donāt do mistakes I will tell you if something chagesā¦ but there is a problem. When I told you that it was slow I didnāt mean that it freezes. It just blocks and move jerkily, I very rarely saw the āballā, or well, there are some spinning beach ball when it moves like a pregnant elephant, but they are not in the screen anyway I will do it as soon as I receive the 2 new memories and then I will tell youā¦ or there is any other matter (now 1,30 GB of memory but I am doing nothing since I am on the forum)?
Come on, 1,37 GB, who offers more?
Since you talked about working with high resolution images, my assumption is that thereās a memory leak related to image handling.
Is GarageSaleās memory usage slowly, but steadily growing - or are there certain actions that trigger a bigger leap in memory consumption, e.g. selecting a listing containing big images, editing images, rotating images, launching listings?
I noticed it was constantly increasing, both if I list or not use GS. I started this morning with about 500 MB, now it is about 1,50 GB. There are some actions especially jerkily. When I am on a listing and I click on another one active to see its contents it requires several second to show them. However I donāt find any slow action while listing (I fill all fields and start without problem). I donāt modify image inside GS, I do it before.
Hope this helpsā¦
It reached about 1,60 or more GB, I closed it and reopened, now it is only 60 MB.
Definitely poor code 128GB RAM with 2TB SSD but activity monitor is not even moving. Sorry this version of GS is very poor, if it wasnāt for the HTML issues eBay said I had with the last version I would downgrade in a flash.
Nice photo!! Is it yours?
no, sourced by googleā¦
Ah I see 
Anyway, this is a very old thread. Many things changed in the meanwhile and the main problem of the āgetting slowerā was a old iMac with a poor HD. Now I am using a 2015 macbook pro and running almost 6000 listings, and it is undoubtedly faster and faster than the first beta period (the memory leak is fixed for example). I have to say it is no longer fast as GS 6 was, but it is good also without pedalling 
ā¦
As a German company, I appreciate your attention to detail when choosing this foto. 
What makes you think this? Do you see the spinning beach ball a lot?
I searched in our crash database for a crash posted by the e-mail you are using on this forum, but couldnāt find one. Next time, please fill in an e-mail address so we can see what the issue you are running to is.
Crashes / hanging on reading āphotosā takes ages then often crashes. Activity monitor shows almost no CPU movement, disk i/o or RAM usage at same time.
We get a very long delay when first opening the Media window after starting the app, but after that it remains pretty snappy for us. Definitely not experiencing the spinning beach ball of delay overall as much as was with GS6.
