With $ioDebug->:=False load is close to normal without session monitor window open. With session monitor window open I get a small peak in cpu load about every 4s. In-between it is close to zero like with without session monitor open, while with $ioDebug not set (aka defaulting to true as my structure runs interpreted) load was increased whether I had session monitor window open or not.
Only tested on local setup, where cpu increase isn't as dramatic as on the production server. Can test on production server as well during night time, if you like. Peter > Von: Aparajita Fishman <[email protected]> > Antworten an: Active4D Developer Discussion List > <[email protected]> > Datum: Wed, 21 Nov 2012 14:59:11 -0500 > An: Active4D Developer Discussion List <[email protected]> > Betreff: Re: [Active4d-dev] Tracking high cpu load when A4D_Startup is called > on 4D client > >> There is no 4D process reported, that consumes the cpu to that extend, so I > >> assume it is the Active4D plugin. When I pull down a 4D menu on the client >> (which actually freezes the client thanks to old carbon code in 4D), the cpu >> load on the server goes down to normal. > > Sounds like it has something to do with the communication between > client<->server for the console and/or session monitor. What happens if you > set $ioDebug->:=False in A4D_DebugInitHook? > > Regards, > > Aparajita > www.aparajitaworld.com > > "If you dare to fail, you are bound to succeed." > - Sri Chinmoy | www.srichinmoy.org > > _______________________________________________ > Active4D-dev mailing list > [email protected] > http://list.aparajitaworld.com/listinfo/active4d-dev > Archives: http://active4d-nabble.aparajitaworld.com/ _______________________________________________ Active4D-dev mailing list [email protected] http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://active4d-nabble.aparajitaworld.com/
