Stepaan Posted March 29, 2021 Share Posted March 29, 2021 Please, could someone help me? I'm preparing some stuff in the Publisher. And I wonder, why is the RAM usage so high. All my images are linked none is embeded. But I get a full memory right after opening the afpub file i'm working on for several days. And I mean totally full. No other piece of software demand so much. Even 3D, audio, video applications. It happens only with the Publisher. Is it normal or is it some sort of bug? Thank you. Quote Link to comment Share on other sites More sharing options...
Pšenda Posted March 29, 2021 Share Posted March 29, 2021 33 minutes ago, Stepaan said: All my images are linked none is embeded. Whether images are embedded or linked affects only the size of the file (whether it contains the entire image or only a link to it). However, "all" image data must be loaded, stored in memory (in uncompressed form) and displayed, when the file is processed. Quote Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.4.0.2301 Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155. Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155. 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. Link to comment Share on other sites More sharing options...
Pšenda Posted March 29, 2021 Share Posted March 29, 2021 41 minutes ago, Stepaan said: Is it normal or is it some sort of bug? How many pictures and how big are they? (Not how big the files are, but how many pixels and what bit depth these images have). And how much memory do you have? Maybe you will be able to calculate it yourself - that it is normal :-) Quote Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.4.0.2301 Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155. Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155. 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. Link to comment Share on other sites More sharing options...
Seneca Posted March 29, 2021 Share Posted March 29, 2021 3 minutes ago, Pšenda said: However, "all" image data must be loaded, stored in memory (in uncompressed form) and displayed, when the file is processed. That may be true but that doesn't necessarily mean that all images have to be stored in memory all the time. Good memory management implies that pictures are loaded when they are needed to be shown on the screen and swapped out when they are not needed any more. Quote 2017 27” iMac 4.2 GHz Quad-Core Intel Core i7 • Radeon Pr 580 8GB • 64GB • Ventura 13.6.4. iPad Pro (10.5-inch) • 256GB • Version 16.4 Link to comment Share on other sites More sharing options...
Pšenda Posted March 29, 2021 Share Posted March 29, 2021 3 minutes ago, Seneca said: Good memory management implies that pictures are loaded when they are needed to be shown on the screen and swapped out when they are not needed any more. Yes, and then reload when the user returns to the same page, and then delete and reload another image again, and then delete and reload again,.... until the disk is destroyed (not to mention the low processing speed of continuous loading). In my opinion, "good" memory management, on the other hand, minimizes the need for disk operations (they are definitely inefficient and time consuming), and uses the maximum available memory. Only if the memory is no longer available will it start to solve - whether the data is really needed or can be discarded (of course with the risk that they will have to be read again). Quote Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.4.0.2301 Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155. Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155. 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. Link to comment Share on other sites More sharing options...
Stepaan Posted March 29, 2021 Author Share Posted March 29, 2021 26 minutes ago, Pšenda said: How many pictures and how big are they? (Not how big the files are, but how many pixels and what bit depth these images have). And how much memory do you have? Maybe you will be able to calculate it yourself - that it is normal 🙂 I'm preparing my portfolio. So it's quite mixed. From simple JPGs, through PSDs to print PDFs. So if I understand correctly, Affinity apps just need all the data stored in memory, so they can perform all the tasks we love. It's not possible with lowres "dummies" (or how to call it) 9 minutes ago, Pšenda said: Yes, and then reload when the user returns to the same page, and then delete and reload another image again, and then delete and reload again,.... until the disk is destroyed (not to mention the low processing speed of continuous loading). In my opinion, "good" memory management, on the other hand, minimizes the need for disk operations (they are definitely inefficient and time consuming), and uses the maximum available memory. Only if the memory is no longer available will it start to solve - whether the data is really needed or can be discarded (of course with the risk that they will have to be read again). My SSD is swapping all the time and it doesn't matter if it's re-loading pictures or just swapping because of the insufficent memory. I have 16GB RAM and I never thought I needed an upgrade for simple DTP tasks before. Quote Link to comment Share on other sites More sharing options...
Stepaan Posted March 29, 2021 Author Share Posted March 29, 2021 OK. Would it be a solution if I re-compute all the images using the new feature? What is it called? "Convert pixel layer to image node" Or "Rasterise & Trim"... Quote Link to comment Share on other sites More sharing options...
Pšenda Posted March 29, 2021 Share Posted March 29, 2021 23 minutes ago, Stepaan said: I have 16GB RAM and I never thought I needed an upgrade for simple DTP tasks before. Since you didn't provide an answer to the previous crucial question - how much and how much image data you process (whether it's JPEG or something else is completely irrelevant), it's hard to judge whether it's a "simple DTP tasks", and if the 16GB memory is large enough. Quote Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.4.0.2301 Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155. Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155. 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. Link to comment Share on other sites More sharing options...
Stepaan Posted March 29, 2021 Author Share Posted March 29, 2021 1 minute ago, Pšenda said: Since you didn't provide an answer to the previous crucial question - how much and how much image data you process (whether it's JPEG or something else is completely irrelevant), it's hard to judge whether it's a "simple DTP tasks", and if the 16GB memory is large enough. It's 4 images per page on average, I'm on page 22 now, and still counting Image size is around A4 in most cases. And is it really irrelevant whether it's "flat" jpg or psd with layers or even a print PDF with fonts embeded, raster and vector graphics and so on? I know, everybody must hate this sentence... But... In InDesign, it wouldn't be any issue, since it works with lowres thumbnails. And frankly, I don't see any advantage for this kind of task to work with hires data. Would be the Rasterise & Trim or Convert pixel layer to image node a solution for me? Would I get the (let's say) 300 DPI, 100 % transformed images with a fragment of the original size? Simply put, would I get 1:1 WISIWIG? Quote Link to comment Share on other sites More sharing options...
Stepaan Posted April 2, 2021 Author Share Posted April 2, 2021 I don't think, this is friendly to the SSD EDIT: Rasterise & Trim got me here: The same document, but images are not linked, but embeded as pixel layers. But it's just a workaround, not a solution. Because in this case, I lose an important part of the Publisher's abbilities. 😕 Quote Link to comment Share on other sites More sharing options...
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.