I'm going to update quite a few events for the C # WPF GUI that came to me through an orbit library I'm thinking that I should be suppressing the number of incidents received through a second, so:
1) How many UI modifications of thumb rules updates, its Should be allowed per second? (For example, say 10 seconds) - In my case they will change the values once in the graph (which is, so the bars in the real time will go up / down.)
2) Is it It is ok to throttle the UI side, because it grabs events, or what should be in the class library which creates events? Let's say you want to reuse class library. (I'm assuming that this class is understood to mess up in the library, which you want to maximize events per second per second).
Did you try to update without throttling? Do you see a real performance issue? Or do you expect to see just one? I can not really do anything before I'm sure that I have to do it ..;)
From the other perspective, how many changes can your users actually see / respond? The article shows that humans are originally animated to watch about 13 to 15 frames and upwards. Maybe this update may be a sensible signal for a range of frequency? Hth
PS: As far as I know throttling can be done very well, the reactive extension is being used. It shows something about it
Comments
Post a Comment