Jump to content
You must now use your email address to sign in [click for more info] ×

Developing Performance #240


Recommended Posts

Hi Mark,

regarding the developing performance with a 22.3 MP .CR2 of a Canon 5D M3

Load time:

#135 --> 7.5 secs first time, later then 6.5 secs

#240 --> 4.5 secs first time, later then 3 secs

Developing time without adjustments (default settings):

#135 --> 4 secs all the time

#240 --> 13 sec all the time and I get a "washed" out image (btw. it's 1.5 seconds faster then the previous betas)

 

If you need a sample file, please let me know... Thanks!

Link to comment
Share on other sites

2 hours ago, Mark Ingram said:

pressing the Tone Mapping Persona button...

Ok, I've done a test by using the previous developed .CR2 file:

#135 --> 31 secs first time, all additional attempts by canceling the result and trying it again increases the time by a few seconds (35, 37, 39, 43 seconds etc.)

#240 --> 23 secs first time, then about 45 seconds for the second try after canceling and finally it ended up with a app crash, app freeze or a complete Windows 10 crash with the third attempt. I've tried it a few times, always with the same result.

I assume something with the memory usage...

Link to comment
Share on other sites

4 hours ago, Mark Ingram said:

on my very high spec desktop machine

Not everyone owns such a HIGH SPEC machine !

1.7.0.240
Startup : 29 sec

RAW
Open : .CR2  (18.10 MP) 21 sec - second time: 16 sec
Develop (without making changes) :  50 sec and still washed-out

Tone mapping Persona 
Startup : 10 min 17 sec    !!!!!
APPLY (with minor changes) :  25 sec
 

Affinity Photo  2.3.1

Laptop MSI Prestige PS42
Windows 11 Home 23H2 (Build 22631.3007) - Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz   2.00 GHz - RAM 16,0 GB

 

 
Link to comment
Share on other sites

12 hours ago, IndigoMoon said:

#240 --> 23 secs first time, then about 45 seconds for the second try after canceling and finally it ended up with a app crash, app freeze or a complete Windows 10 crash with the third attempt. I've tried it a few times, always with the same result.

I assume something with the memory usage...

What was the memory usage? Have you enabled the crash identifier in Preferences | Misc? If so I can lookup your crash.

Link to comment
Share on other sites

1 hour ago, Mark Ingram said:

Hi @HVDB Photography, what are the times in the previous beta or the times in 1.6 for your machine?

As I mentioned in the release notes for 1.7.0.240, the performance improvements should scale between high spec and low spec machines. I was clarifying my "60 seconds" timing with the caveat that my machine is very fast anyway.

Here they are ....

1.6.5.123
Startup : 29 sec

RAW
Open : .CR2  (18.10 MP) 25 sec - second time: 25 sec
Develop (without making changes) :  27 sec 

Tone mapping Persona 
Startup : 1 min 27 sec   = A tremendous difference !!!!!!!!!

APPLY (with minor changes) :  19 sec

Affinity Photo  2.3.1

Laptop MSI Prestige PS42
Windows 11 Home 23H2 (Build 22631.3007) - Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz   2.00 GHz - RAM 16,0 GB

 

 
Link to comment
Share on other sites

3 minutes ago, IndigoMoon said:

Sure, it was enabled. Where to find these reports? Regarding the memory usage, it's just an assumption, because of the time accumulation after each try.

A copy of the reports are on your HDD, but I can search for them on our server. I'm assuming your email address (in Preferences) is the same as here on the forum?

Link to comment
Share on other sites

19 minutes ago, HVDB Photography said:

It's all in my signature below ...

 

6 minutes ago, Mark Ingram said:

Your signature is empty...

Not for me! O.o

Quote

Affinity Photo 1.6.5.123

Windows 10 / 64 bit processor - AMD A4-5000 APU with Radeon HD Graphics  1.50GHz - RAM 8,00 GB
Calibrated Monitor (Datacolor Spyder5 Pro)

 

 

Alfred spacer.png
Affinity Designer/Photo/Publisher 2 for Windows • Windows 10 Home/Pro
Affinity Designer/Photo/Publisher 2 for iPad • iPadOS 17.4.1 (iPad 7th gen)

Link to comment
Share on other sites

We think the application is holding onto more memory than it should, which is causing Windows to page (i.e. write the contents of your memory) to disk. That would explain the kinds of slowdown you're seeing. Any chance you can tell me memory usage after developing, or entering tone map persona etc?

Link to comment
Share on other sites

17 hours ago, Mark Ingram said:

We think the application is holding onto more memory than it should, which is causing Windows to page

That confirms what I had in mind for a long time.
The video (at double speed)  shows that once the RAW development has been executed, the memory is not released.
Although, the extremely long time span at the start of Tone Mapping Persona I could no longer simulate!
It now takes an average of just over 3 minutes each time before TMPersona is up and running.
I also have to add that I've done a cold reboot and disabled the Superfetch service beforehand.
 

Affinity Photo  2.3.1

Laptop MSI Prestige PS42
Windows 11 Home 23H2 (Build 22631.3007) - Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz   2.00 GHz - RAM 16,0 GB

 

 
Link to comment
Share on other sites

Yes it seems as though the Tone Mapping Persona is the real culprit:

 

Affinity 240 Tone Map.jpg

Both PC’s Win 11 x64 System with Intuos Pen & Touch 
PC1 ASUS ROG Strix - AMD Ryzen 9 6900X CPU @ 3.3GHz. 32GB RAM

- GPU 1: AMD Radeon integrated. GPU 2: NVIDIA RTX 3060, 6GB
PC2 HP Pavilion - 
Intel® Core™ i7-7700HQ CPU @ 2.80GHz (8 CPUs), 16GB RAM
 - GPU 1: Intel HD Graphics 630, GPU 2: NVIDIA GTX1050, 4GB

iPad (8th Gen) 2020

 

Link to comment
Share on other sites

There are different versions of Windows 10. Microsoft upgrades Windows 10 twice a year, one in spring and one in fall. The latest version is 1809 (stands for 2018 and September). I think it would help to add this to the signature too.

Affinity Photo 2.0.4  |   Affinity Designer 1.10.5.1342 | Affinity Publisher 1.10.5.1342

Windows 10 Pro 22H2 64bit | Intel Core i7 8750H @ 2.2 GHz | Nvidia GeForce GTX 1060 (Studio Driver) | Intel UHD Graphics 630 | 16 GB Dual Channel DDR4

https://www.flickr.com/photos/owlp

Link to comment
Share on other sites

Tested the Tone Mapping with the 240 Beta last night just before dinner. It hung going into the Tone Mapping Persona at roughly 40%, not quite half way. I left it, ate dinner and returned about 40 minutes later. It had not progressed, and in fact almost caused my entire system to crash, couldn't bring up Task Manager. I did finally manage to force close Photo. I still had to reboot my machine to get it to working smoothly again.

This morning, I noticed just 4 minutes after Mark posted the 243 Beta link. Download/Installed, and tried Tone Mapping first, using the same CR2 RAW file as I used last night. WOW what a difference. 12 secs to load into Tone Mapping. Done a few adjustments, then hit develop and 3 secs to develop and back to working in Photo Persona.

Good Work @Mark Ingram

Affinity Photo 2.4..; Affinity Designer 2.4..; Affinity Publisher 2.4..; Affinity2 Beta versions. Affinity Photo,Designer 1.10.6.1605 Win10 Home Version:21H2, Build: 19044.1766: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz, 3301 Mhz, 6 Core(s), 12 Logical Processor(s);32GB Ram, Nvidia GTX 3070, 3-Internal HDD (1 Crucial MX5000 1TB, 1-Crucial MX5000 500GB, 1-WD 1 TB), 4 External HDD

Link to comment
Share on other sites

OK!

Both PC’s Win 11 x64 System with Intuos Pen & Touch 
PC1 ASUS ROG Strix - AMD Ryzen 9 6900X CPU @ 3.3GHz. 32GB RAM

- GPU 1: AMD Radeon integrated. GPU 2: NVIDIA RTX 3060, 6GB
PC2 HP Pavilion - 
Intel® Core™ i7-7700HQ CPU @ 2.80GHz (8 CPUs), 16GB RAM
 - GPU 1: Intel HD Graphics 630, GPU 2: NVIDIA GTX1050, 4GB

iPad (8th Gen) 2020

 

Link to comment
Share on other sites

×
×
  • Create New...

Important Information

Terms of Use | 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.