Our FR5 monitor freezes when its diagnostic folder gets busy

I asked for more detailed logging to help with a sluggish read-only monitor. Now the display sometimes sits still while its log folder is busy, then several entries appear together. Marvellous, more detail and less idea of when anything happened. The cell controls are separate and keep doing their job. What should our developer time to distinguish waiting for a response from waiting to write the log, before somebody sells me a faster laptop?