Hi All

Somme feedback:

Just did an event and had a ranking title (top 8) driven by datasources set Rows to columns.
the file was an XML had 40 record in the end and response time (data showing up ) became really slow : up to 30 seconds !
refresh set to 1000 (1 sec) . While i understand some delay might be expected but half a minute is quit some delay especially in fast acting and updating need situations imo .

mind you using the datasources as standard were very efficient , helpful and practical !

Guy

Thanks for the feedback Martin

Datasource manager was closed btw.
Due to lack of time to create a external reader into the .dll title we opted for the datamanager for this particular display
Same data was pulled from another "title" with its own reader embedded for a ranking update with no delay noticeable at all

I just did a simulation with the last entry ( who in fact became the winner at the event) with and without the datamanager open and indeed it acts according to your explanation ( open versus closed )
The strange thing is i am convinced we didn't have the manager open , as all was preset and as such no need to open the manager at all .
Than again in the heat of the moment as each update was close to 1 minute apart we could had inadvertently opened it to check and forgot to close , if so than i apologize while i can also see a slowing down happening over time ; 4 rounds , each 40 participants , in final ranking title we had top 8 displayed and each had 5 fields updated.starting anew after each round .
My current test was of course updating this last record and not after 160 additions/changes as during the event

If indeed having the datamanager open is the key we will run into this issue again as the plan was to have also an excel datasource open with the info list we needed to manually select records from of all participants for a lower third . As it happened this was done on another laptop as an emergency (not related to this) and the footage with the lower third info send via NDI (the lifesaver) to the laptop with the ranking and ultimately streamed with the ranking laptop hence the manager should not have been open on the laptop with the issue .

Reason we thought it could have been a build up of delay is that a similar situation happened when sending lots of fast httprequests to the streaming /title laptop which initially was instant updating but over time got slower and slower until we quit sending the requests to not come to a complete standstill. Mind you a clock we interfaced with was able to cope with the fast updating through httprequests (1/10 sec) while another also with a stopwatch data sending (and other title data) came to a crawl. probably not related to the httprequests by itself but some issue in general with the overall programming code (got some debugging to do :-) )

So any hints on dealing with lots and fast httprequests (clearing something ? ) if this is part of the issue would be very helpful for the future aside the knowledge to close the datamanager ( not always practical but still good to know to change strategies) .

Guy