SG Pilgrim Posted January 26 Posted January 26 (edited) This isn't really a bug, that I'm aware of, it's likely more just an issue of performance. However, I am surprised at how long it takes to export this artwork to a single layer pdf. Is there a way to move the processing to the GPU? What portions of the software suite use the GPU versus the CPU? This CPU only has 8 cores, but because of how long this is taking to export files I'm beginning to consider downgrading to an older processor with more cores. Anyone have CPU suggestions that won't cause the wallet to have a heart attack? Note: the filenames have the time in the name. Screenshot #1 2025 01-25 @ 1901 -- initial screenshot showing what is running on the system Screenshot #2 2025 01-25 @ 1910 -- begin 100% cpu usage Screenshot #3 2025 0125 @1919 -- export of pdf finally completed * this also happens when exporting a jpg, so I'm sure there is something to do with rasterizing everything that is part of the issue. Other exports, if I remember correctly take as long, or nearly so. I would have to run a couple more tests just to be sure but it's late and I'm done for the day. My System AMD 7800 3D 64GB RAM Nvidia RTX 4090 Samsung 980 Pro 2TB (os/apps) Gen4 m.2 Crucial T700 SSD Gen5 m.2 Affinity Suite 2.5.7 Windows 10 Pro Version 22H2 Installed on 12/5/2024 OS build 19045.2965 Experience Windows Feature Experience Pack 1000.19041.1000.0 Screenshot #1 Screenshot #2 Screenshot #3 Sorry for the messy layers panel... Edited January 26 by SG Pilgrim remove duplicate screenshot Quote
carl123 Posted January 26 Posted January 26 Probably best if you can upload a sample Affinity document and a screenshot of the export settings you use plus let us know how long it takes to export on your system Quote To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.
Alfred Posted January 26 Posted January 26 1 hour ago, carl123 said: let us know how long it takes to export on your system We’ve already been told (twice!) that it takes nine minutes. Quote 9 minute export with 100% cpu usage -- designer 2.5.7 … Screenshot #2 2025 01-25 @ 1910 -- begin 100% cpu usage Screenshot #3 2025 0125 @1919 -- export of pdf finally completed Quote Alfred Affinity Designer/Photo/Publisher 2 for Windows • Windows 10 Home/Pro Affinity Designer/Photo/Publisher 2 for iPad • iPadOS 17.5.1 (iPad 7th gen)
carl123 Posted January 26 Posted January 26 1 minute ago, Alfred said: We’ve already been told (twice!) that it takes nine minutes I ask them to upload a sample file which did not have to be the one they were talking about (may have been private) So, I needed the time for that file Alfred 1 Quote To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.
Alfred Posted January 26 Posted January 26 Just now, carl123 said: I ask them to upload a sample file which did not have to be the one they were talking about (may have been private) My bad, I overlooked that ‘minor’ detail! Quote Alfred Affinity Designer/Photo/Publisher 2 for Windows • Windows 10 Home/Pro Affinity Designer/Photo/Publisher 2 for iPad • iPadOS 17.5.1 (iPad 7th gen)
Pšenda Posted January 26 Posted January 26 2 hours ago, SG Pilgrim said: Screenshot #2 Try change view to logical CPU core. Quote Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.5.7.2948 (Retail) Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 24H2, Build 26100.2605. Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 24H2, Build 26100.2605. Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.
Andy05 Posted January 26 Posted January 26 4 hours ago, SG Pilgrim said: This CPU only has 8 cores, but because of how long this is taking to export files I'm beginning to consider downgrading to an older processor with more cores I have an AMD R9 7900x (12 cores), but my GPU isn't remotely as strong as yours (RTX 4070ti OC). If you want me to test it with your files, feel free to contact me directly in case you don't want to share the file publicly. I'll delete it immediately after testing the export. Quote »There are three responses to a piece of design: yes, no, and wow. Wow is the one to aim for.« Milton Glaser (1929 - 2020)
NotMyFault Posted January 26 Posted January 26 Can you try exporting from Affinity Photo? GPU utilization differs for both Apps. You file seems to contain lots of bitmap layers, Photo might get an edge. Quote Mac mini M1 A2348 | MBP M3 Windows 11 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080 LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5 | Dell 27“ 4K iPad Air Gen 5 (2022) A2589 Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps. I use iPad screenshots and videos even in the Desktop section of the forum when I expect no relevant difference.
SG Pilgrim Posted February 3 Author Posted February 3 My apologies for the slow reply. The file in question isn't private, so I can share it here. When testing, I prefer to use actual files as any changes tend to skew the results. However, @carl123 I appreciate the concern for potentially private design work! It was very interesting, as I had only been using Designer (unless I needed to create a mask for an image) as I found it to be quite a bit better at resource usage. I made a poor assumption that they using the same export engine under the hood. However, after thinking about it for 5 seconds, it makes perfect sense there would be quite a difference being one is supposed to be for vector work and the other, obviously for raster based work. Note: Please forgive the statue in the document, it's hideous (in my opinion). I tried to get it changed to something a bit more representative of reality, but was overruled two or three times, so it stays. Note 2: I think it's simply a matter of the huge background image that needs to be processed. I had forgotten how large I had made the image to get the texture I wanted. @NotMyFault The time needed to export from affinity photo was significantly less, about 3 minutes - that's a huge improvement! However, it doesn't handle bleed well, so the exported files (other than this one) I've still needed to export from Designer. @Pšenda I had forgotten to do that previously, however, the results are still the same. All cores running at 100% cpu utilization for ~9 minutes. @Andy05 With 12 cores I wouldn't expect a huge improvement on the render time, but I would still be curious to see the difference. Thanks for testing it! Rollup Daniel 2 MASTER v2-1.afdesign Quote
carl123 Posted February 3 Posted February 3 The main problem is the "Stone" layer/group. It has multiple live adjustments and filters applied to it which slows the export down Just right-click the group shown below and select Rasterise & Trim and future exports will be a lot faster Note: Rasterise & Trim may take a minute or 2 to complete due to all those live layers Quote To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.
Pšenda Posted February 3 Posted February 3 (edited) 7 hours ago, SG Pilgrim said: the results are still the same. All cores running at 100% cpu utilization for ~9 minutes. Switching the "view" to logical cores can of course have no effect on the export speed, but it should show how and how many cores are involved in the export. Unfortunately, this is not apparent from your screenshot, because it is not done under load. Now I noticed that although the graphs are mostly at zero (which led me to the impression that the screenshot was not taken during export), the total CPU load is 100% (+ export progressbar). This means that only one core is used during export (but perhaps a record after a longer export period would be useful, so that the graphs are more conclusive) - which probably also answers your original question, whether it makes sense to switch to a processor with more cores. P.S. Interesting - when I export your file, all processor cores are being used. If the export includes a large image, then enabling HW Acceleration could have an effect. Edited February 3 by Pšenda Quote Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.5.7.2948 (Retail) Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 24H2, Build 26100.2605. Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 24H2, Build 26100.2605. Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.
Andy05 Posted February 3 Posted February 3 The export took less than 2 minutes on my system and the core's load was all over the place (jumping between 8% and 100% and 3000+ to 5650 MHz over all cores). But I tried it with the current beta, so I don't know, if that makes any difference. Quote »There are three responses to a piece of design: yes, no, and wow. Wow is the one to aim for.« Milton Glaser (1929 - 2020)
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.