• Replies 4 replies
  • Subscribers 582 subscribers
  • Views 302 views
  • Users 0 members are here
Options
Related

Citect 2018 Startup Time

Steve

Hi community,

Does anyone know what Citect Studio does when it first launches the graphics builder (and performs some preload operation) and whether it's possible to speed this process up (or avoid it completely)?

Depending on the machine we're running on, it could take up to 10mins (or longer) for the graphics builder to become usefully responsive.

Parents
  • My guess is that Citect is doing something at startup that involves the composite genies. As the number of composites (and pages using them) we have in our project has increased, so has the startup time. Throughout this period there are 'Keyboard' and 'Animation Point' prompts in the status bar of the graphics builder.

    A ProcMon dump seems to corroborate this. Starting Citect Studio produces the following:
    1. Lots of accessing various DBFs/NDX/INI in various projects for a short period (<2sec)
    ...followed by the 2a/2b sequence over and over again (for 10mins)...
    2a. CTDRAW32.EXE accessing a CTL or CTM at a specific file offset and reading a block of data (usually in extremely small 4bytes chunks)
    2b. CitectIDE.EXE accessing the associated project's PROJECT.CIT file (for a very short period; <0.1sec)

    The vast majority of the trace activity is CTDRAW32.EXE reading CTM files in small chunks, and it does this consistently for the entire duration (ie. there aren't any periods where it is not doing this).

    The problem is consistent across multiple machines with completely different builds; aside from all being Windows 10.
    Machines are 64bit i7 2.2GHz or better, 32GB RAM, 256GB SSD; or VMs of the same ilk.
Reply
  • My guess is that Citect is doing something at startup that involves the composite genies. As the number of composites (and pages using them) we have in our project has increased, so has the startup time. Throughout this period there are 'Keyboard' and 'Animation Point' prompts in the status bar of the graphics builder.

    A ProcMon dump seems to corroborate this. Starting Citect Studio produces the following:
    1. Lots of accessing various DBFs/NDX/INI in various projects for a short period (<2sec)
    ...followed by the 2a/2b sequence over and over again (for 10mins)...
    2a. CTDRAW32.EXE accessing a CTL or CTM at a specific file offset and reading a block of data (usually in extremely small 4bytes chunks)
    2b. CitectIDE.EXE accessing the associated project's PROJECT.CIT file (for a very short period; <0.1sec)

    The vast majority of the trace activity is CTDRAW32.EXE reading CTM files in small chunks, and it does this consistently for the entire duration (ie. there aren't any periods where it is not doing this).

    The problem is consistent across multiple machines with completely different builds; aside from all being Windows 10.
    Machines are 64bit i7 2.2GHz or better, 32GB RAM, 256GB SSD; or VMs of the same ilk.
Children
No Data
© 2025 AVEVA Group Limited or its subsidiaries. All Rights Reserved.