We are using the AspxScheduler Control in our project, to publish timetables, floorplans and horizontal bar diagrams using TimeLineView. Since some months, many customer complain about the speed, the Control publishs the data in our web application. In some situations, the browser stops running javascript and shows critical error messages after Databinding. Our customer want to publish a lot of data in one Scheduler-View, sometimes up to hundreds, thousand and more items.
So I have searched for reasons, why the Control needs sometimes up to 1 minute, to publish data. In my web project I use the same way to publish data as in your demo project, using the ObjectDataSource:
http://localhost/ASPxSchedulerDemos_v9_3/VB/ASPxSchedulerDemos/ViewTypes/TimelineView.aspx
So I have changed two parameters in the demo project, to reproduce the problem:
a. in the web.config I have changed at line 17 the value to true : <add key="SiteMode" value="true"/>
b. in App_Code/DemoUtils I have changed at line 67 the value of count to 1000, or maybe 10000
With this changes I try to start the page TimelineView.aspx, but after maybe 30 / 40 seconds the browser asks to stop the running scripts. This situation is significant monitored in the Internet Explorer, but also Firefox and other browser seems to have problems in publish a lot of items at one time.
So I have to ask, whether the kind above of publish data is the right one in this situation? Maybe, is the Control the right one to publish the amount of items at one time?
My expectation, and the expectation of my customer, is publishing data in a few seconds, at best up to 10 seconds.
Can you reproduce the situation? Can you show me a solution, a way in publish the data much faster?
Thanks for your coming answer, Guido.
Ticket
B146789
Visible to All Users
Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
Hi Guido,
Please handle the ASPxScheduler.FetchAppointments event to manually provide the scheduler storage with appointment data. This can be useful when working with a large amount of data, and only a small part of it needs to be loaded at one time. Also, please review the How to enhance performance when handling a large number of appointments (ID:E489) code example for additional information.
Thanks,
Elliot
Hi Elliot,
thanks a lot for your work. Working with parameters reduce the count of items now, but the described behavior still exists. As an example, the ASPxScheduler Control in TimelineView will display up to 1000 items. That's not possible, because the browser stop the running javascript and ask the user to going on (see screenshot.jpg). All items in the datasource meet the conditions, by working with paramters.
Do you know a work-around, maybe a work-around to hide the describe popup-message, setting a greater timeout value?
Thanks in advance for your work …
Hi Guido,
Thank you for the reply.
Please review following articles, which illustrates how to increase the timeout value:
Error message: "A script on this page is causing Internet Explorer to run slowly"
How to extend browser script timeout
Thanks,
Elliot