Ultimately it depends on how powerful your computer is. A cheap laptop won’t be able to run the DevKit either at all or so poorly it’s just not worth it, and the same can be said for cheap-o brand name machines that big-box stores usually sell.
Still, there are some things inherent to the DevKit that will bog it down, especially the first time you try to do something every time you open it. When you try to right click on a file, copy a file, open a file or move it, the DevKit will freeze/lock you out while it loads all connected assets, and some general ones pertaining to the engine itself, into memory(your RAM usage will spike while this is happening).
My advice always has been that when you open the DevKit, jump straight into a PIE session(click the “Play” button to enter the test map) - the DevKit will freeze with this too - and once you’re in, “stop” or get out of it(just press Esc) then things should become a lot smoother.
If even after that the DevKit is extremely slow and sluggish to inputs, then it’s entirely possible, and likely, that your machine is just not all that capable of running it. And nothing can be done if that’s the case - bar getting a new machine.
It is a beast of a program and is a cut down version of what WildCard use for ARK, so it has some serious performance requirements to make the best use of it.
-WM