Slow Startup Times?
Posted: Sun Nov 06, 2016 23:10
I'm not reporting this as a bug because I have no idea if it is or not. It may even be system specific to me (I can't find another post about it). However, the first time I start GZDoom 2.2.0 (either 32 or 64 bit) there is a lag of pretty close to 9-10 seconds before anything seems to happen.
If I double click the exe directly, there is about a 9-10 second delay and the windows cursor may become the rotating blue circle then the GZDoom startup window appears with the IWAD selection dialogue on top of it (i.e. from that point on, things are normal).
Launching via ZDL, again there is the 10 second delay and clicking anywhere on the ZDL window changes its title bar to read "not responding" then GZDoom starts (the IWAD being added to the command line by ZDL).
It seems as if there might be some sort of caching thing going on. If I quit and then restart GZDoom immediately, there is no startup delay. However, if I quit, do something else for a while and then try GZDoom again I get the delay. I've tried with gl_cachenodes on and off: no difference. However, that's not a big surprise because the delay seems to happen before any WAD data is loaded. Also, quitting and specifying a different IWAD in ZDL allows a non-delayed start with the chosen IWAD. Once the game has started, it works just fine.
I don't seem to be experiencing this with other ZDoom engines or older versions of GZDoom. I'm not entirely sure yet if it's happening with the current DRD builds of GZDoom because I'm not sure how long or what I need to do to clear the memory to get it to happen but I *think* the DRD builds might be OK.
So, is this something other people have noticed or is it just me?
Spec:
GZDoom 2.2.0 32 or 64 bit
CPU: i7 Six Core Processor 6800K (3.4GHz) 15MB Cache
Memory: 16GB HyperX FURY DDR4 2133MHz (4 x 4GB)
Graphics: 8GB NVIDIA GEFORCE GTX 1080
Sound: Onboard HiDef Audio (7.1)
OS: Windows 10 Professional 64 Bit
If I double click the exe directly, there is about a 9-10 second delay and the windows cursor may become the rotating blue circle then the GZDoom startup window appears with the IWAD selection dialogue on top of it (i.e. from that point on, things are normal).
Launching via ZDL, again there is the 10 second delay and clicking anywhere on the ZDL window changes its title bar to read "not responding" then GZDoom starts (the IWAD being added to the command line by ZDL).
It seems as if there might be some sort of caching thing going on. If I quit and then restart GZDoom immediately, there is no startup delay. However, if I quit, do something else for a while and then try GZDoom again I get the delay. I've tried with gl_cachenodes on and off: no difference. However, that's not a big surprise because the delay seems to happen before any WAD data is loaded. Also, quitting and specifying a different IWAD in ZDL allows a non-delayed start with the chosen IWAD. Once the game has started, it works just fine.
I don't seem to be experiencing this with other ZDoom engines or older versions of GZDoom. I'm not entirely sure yet if it's happening with the current DRD builds of GZDoom because I'm not sure how long or what I need to do to clear the memory to get it to happen but I *think* the DRD builds might be OK.
So, is this something other people have noticed or is it just me?
Spec:
GZDoom 2.2.0 32 or 64 bit
CPU: i7 Six Core Processor 6800K (3.4GHz) 15MB Cache
Memory: 16GB HyperX FURY DDR4 2133MHz (4 x 4GB)
Graphics: 8GB NVIDIA GEFORCE GTX 1080
Sound: Onboard HiDef Audio (7.1)
OS: Windows 10 Professional 64 Bit