Jump to content

stevelees

Members
  • Content Count

    6
  • Joined

  • Last visited

  1. The bottleneck in this case is rather simple: The Mac uses all CPU cores when opening a file, and exporting a JPEG. The Windows version uses a single core for both tasks. To me at least that has nothing to do with the number of variations they need to contend with in the Windows world, but rather a simple command they have set to use one only. I say this as it clearly uses all 32 cores when running the test here: https://forum.affinity.serif.com/index.php?/topic/32907-affinity-photo-performance-comparison-data-sheet/?p=198410 So why allow ALL CPU cores for many of the tasks in the above test, and limit it to one on the tasks you do every time you use AP? (ie: Opening a file!)
  2. Hi Meb, Thank you for the welcome! I guess that makes some sense given the recent birth of the Windows version. I ran the test that was listed here: https://forum.affinity.serif.com/index.php?/topic/32907-affinity-photo-performance-comparison-data-sheet/?p=198410 It would seem that overall the performance I am getting is pretty impressive on that test, but I think real world daily functions such as file opening and JPEG exporting would have been the first things addressed rather than an after thought. If I can make a suggestion, it would be great to have a PREFERENCE setting in the performance part to choose how much of the computers resources are to be assigned to the Affinity Photo, but then again it does grab everything the machine has to offer for certain tasks, so it is bewildering that the basic functions are so slow. Anyway, I hope it is addressed soon as I have removed Adobe from my life and have no regrets, I just want to see Affinity go from strength to strength and fixing things like this would go a long way towards it I think.
  3. I recently dumped Mac (and Adobe) for Windows/Affinity and spent big money on a HP Z840 with 2 x Xeon 2.1GHz processors each with 8 cores and 16 multi-threaded cores, (totalling 32 CPU cores running as 2.1GHz) 32GB RAM, Nvidea GTX 1080i Video Card, running on an ultra fast HP SSD (3000MB/s read speed/2000MB/s write speed). A friend came over today and we compared speed of Affinity Photo opening a very large PSD file, and saving a JPEG of that file. He had his 4 year old Macbook Pro running an old 4 core i7 at 2.6GHz, with 8 multi-threaded cores. The result was embarrassing.....His old laptop opened the 8GB file much quicker than my machine which has more cores and a way faster SSD. Saving the JPEG file was also much faster on the Mac. What I noticed was that the windows machine uses only a single core for the opening of a file, and only one core for the saving of the file, whereas the Mac used four cores. Why? We then compared the speed when doing a gausian blur on the file, we started both at the same time and all 32 cores on my Windows machine ran at 100% and the progress bar flew to the end and sat there doing seemingly nothing, (just when I thought it was going to annihilate the Mac) but I noticed it then switched back to using a single core to do what exactly I do not know, but it allowed the old Mac to catch up, making the time difference minimal. The Mac was using all 8 cores for this process. So, my question is, WHY is the Windows version seemingly limited to single core for certain tasks, making it's performance hobbled on a machine like the Z840? My preference for ANYTHING I do is to have the app I am working in making full use of all resources on my machine and Affinity is not doing that at all times, yet you allow it on Mac, makes no sense....what am I missing?
×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.