I'm 3rd party IT Support for a company and they've got CorelDRAW 2022 on 2 computers. When opening a file (of any size), where it be 9mb or 400mb, everything is lightning quick. There's no performance issues at all, but within about 30 seconds to 2 minutes, it gets laggy and jittery. They have CorelDRAW 2020 on a weaker PC and it does not happen on this PC.The specs of the 2 computers are as follows:Ryzen 7 2700X8GB RamGTX 1650 128GB NVMe SSDThe older computer is identical but has a GT 710. I'm very confused as I've double checked everything on the computer and it doesn't seem to be a hardware issue. Hardware Acceleration is on, the GPU is set to be used, the settings in CorelDRAW are set to use the GPU for everything it should, I've set the power options to high performance, memory is sitting at about 70%. The only thing I can think of is that the SSDs have about 5% of their space left. Would this cause the performance degradation?Any answers as to why could be very helpful so I can report back to them and help, as I've exhausted all the options I'm familiar with.
Insufficient system, I would avoid anything AMD, I use IntelnI9 withn64 GB RAM and a true NVidia card and 2TB Samsung SSD.
David Milisock said:I would avoid anything AMD
Well some of us avoid everything Intel because it puts Israel inside! No other reason is required!
I've seen zero issues with AMD processors. That is perhaps not the case for AMD graphics cards. How well Corel have managed the difference between OpenGL and the Nvidia system is just unknown to users.
David this Intel insistence is troubling! You don't know and nor do I, what systems Corel are using for their testing. But we can say that AMD processors and GPUs are used for programs that thrash a system well beyond what Draw does.
5% free space on a 128Gb is not good. Have you deleted all temp files and done a clean up to remove junk like old patches?
Next run task manager and check memory. What is the "reserved hardware memory"? Should be a small number like 40Mb. If not the you have a memory issue to resolve. One that isn't detected with any memory checking tool I've ever found. If that is the issue we can talk about that specifically.
What you need when chasing these errors is extra hardware that you can swap.
And you are running it on 8Mb of RAM. Most of us are running 32Gb of RAM.
All that said, it does sound like some sort of memory leak. Perhaps one that can be ignored when you have 32Gb of RAM.
I'm not in the US, and it's not critically under powered. It works perfectly fine for everything else.You haven't really helped at all here. It appears to be the drive that's causing the issues, not the CPU, not the GPU.
To add onto this, we don't charge per hour for those in our support contracts, which this client is. I've spent my spare time looking into the issues for them.
To add onto this again, a system with worse specs is running CorelDRAW 2020 on the same CPU, but with a 512GB SSD and there's no performance issues at all. It's definitely the drive.
I'm using an old AMD 8 core and apart from video editing renders, it's still an 8 core 4+Ghz processor that's fast. Draw might be multi-threaded etc but that is in context to some pretty basic stuff. I've never seen it make even this processor work hard.
Any old graphics card and 8 Gb of RAM works fine. The program was written to run on the smell of an oily RAM rag. That said, my AMD graphics card can use 16Gb of system RAM + its own 8Gb. You do get more bang out of Windows with a base of 16Gb. I wouldn't be telling anyone to run Windows 10+ on less than 16Gb. Not sure what difference you can prove on that but it is my "happy place". I know I can have whatever running at the same time.
Go for a slow internet connection and run a few MS tools. Go outside and have a cigarette as they run.
"Oh dear we will have to run
DISM.exe /Online /Cleanup-image /Restorehealth
This might take a while..." Prepare to ring the till! :)
Never seen it do anything useful but if you write it on the back of your hand and look all pro type, a command line from memory without a cheat sheet is worth at least $100!
And if they protest too much then you will just have to do a full X2 memory check, lucky they only have 8Gb.
I always start with the pencil rubber and cleaning all memory and card contacts. 50% of all computers I've ever fixed were made go with a pencil rubber. New RAM -- pencil rubber the contacts. Old RAM the same.
The real *** of an issue on my machine that took a year to understand is memory slots.
I had 2 big Nvida cards in the computer. They were 2mm over the RAM clips. Needless to say over many year I've broken the click things on the RAW slots.
Short version... me "make sure that RAW is pushed all the way in".
Turns out that all the way in is perfect for a RAM test. But I get whole modules cast off by Windows as "hardware reserved". I've Googled the hell out of it and found no answers.
What I have found is that if I put the RAM all the way in then feel it back just a bit, hardware reserved drops to a normal number.
Given that all the way in RAM passed every memory test known to man but that somehow Windows decided it "wasn't good enough" and threw it back at hardware, this is my #1 go to before any other type of memory test.
I'd add the pencil rubber and the check of hardware reserved RAM to your general playbook.
Maybe skip the Microsoft tools unless you really hate the client.