What type of data are you using? What type of geometry is it? Polyline, Polygons, Points, Mixture of all different types?
1) Filter data based on extent and the type of data that would be relevent at that extent.
2) you can increase the tolerance of your geometry request to return less complex geometry. e.g. at a city level you might want a polygon of a lake to return all its points so that it is very acurate, but at the world level you really don't need all points to define the shape of the lake that is now 10px wide and tall. As you pan/zoom all in view points have to be translated/scaled, so if you request your geometry based on your veiwing extent you can control how complex the geometry and increase performance.
3) TimeSlider allows you to create intervals which you can use to place an interval every 500 DateTime if you wanted this will help control the amount of data you have visible at one time.
4) Avoid rendering all graphics at one time if possible, and try to render graphics based on a relevent extent.
With large datasets there is no one solution, It all depends on what type of data you are working with and trying to filter data down to what is relevent based on the Extent the user is viewing and How complex the geometry needs to be at that viewing extent.