(02-19-2023, 11:11 PM)PixLab Wrote: Anyway, How much did you allocated to GIMP? (Edit > Preferences), maybe increase it...Tile cache size is best kept smaller than the available RAM, otherwise you overlap system swapping and Gimp swapping and this ain't going to be pretty.
@OP otherwise I concur, your PC is completely underspec'ed for an image this size (mine, which is fairly decent, is hardly sufficient already). As Gimp tells you, the resulting memory usage is almost 15GB and this is before Gimp does anything with the image... So, whatever you do you will likely need more than the 16GB (RAM+Swap). And this is only the beginning of the story, because with such a small RAM, I assume the CPU is a low-end one, and the SDD (assuming it is a SSD and not a good old rotating hard disk) isn't going to be the fastest around, so any processing is going to take a solid hour, assuming it ends without crashing the system(*).
But the real question is, what is printed at 2400DPI? There are very few printers with that kind if resolution(**) and people who use them can have rather lavish PCs. Consumer-grade "2400DPI" printers are really 300PPI (Pixels Per Inch), but each pixel on paper is a 8x8 matrix of ink dots.
(*) Modern system protect themselves by having a rather cavalier attitude: when an application asks for memory, the system always agrees, even if it hasn't got the resources, because very often 1) the app will not use all the memory it asks for, and 2) before it does another app could return some. But if these hopes don't come true, it is too late for the system to tell the requesting app, so instead it kills an app to recover its memory (often the one that requested something big), or just kills the app to which it cannot give the promised memory..