Databases
StackOverflow2013
Postsdbo
POUI Dispatch Buffering?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUI Dispatch Buffering?
    primarykey
    data
    text
    <p>I have a conundrum. I have "inherited" a very badly designed and very complex system which I am modernizing and rebuilding (with my team) piece-by-piece. The problem is that the current system is depended on by 200+ users, and they are having major issues with performance due to the (lack of) design. The most problematic issue at the moment is that a significant amount of work is beng placed on the UI thread, which leads to the GUI hanging until the thread is cleared amd message pumping can continue. Much of this work actually does need to be on the GUI thread, as it is updating a large number of fields in a grid due to other calculation results on other threads.</p> <p>The issue is this: I do not have the resource to dedicate to re-writing the threading model and underlying classes involved here, and the complexity of that work would introduce significant risk which is unacceptable to my client. </p> <p>I wanted to know if anyone had any suggestions on how to make the UI more performant, without interfering too much with the currnet threading model.</p> <p>My initial thought is that there might be some way to put a "buffer" in front of the actual invokes to the UI thread to make sure that the GUI does not get overloaded, or when it does to back off the dispatches to it.</p> <p>Any suggestions would be greatly appreciated. </p> <p>I know none of this is ideal, but we are where we are, and I really want to give my users a better experience prior to the year-long re-write's completion!</p> <p>Thanks!</p> <p><strong>Update #1</strong> This is a winforms app...sorry this wasnt clear at the outset. New code is WPF, but these modules are winforms.</p> <p><strong>Update #2</strong> I am thinking I may initially try changing most BeginInvoke calls to the UI thread to Invoke, introducing a serialization that will hopefully increase UI responsiveness. Any (non-obvious) downsides here, that anyone can forsee?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USmiguel
    1. USmiguel
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POUI Dispatch Buffering?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POUI Dispatch Buffering?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POUI Dispatch Buffering?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COMaking the asynchronous calls synchronous is effectively moving back to a single-threaded approach. Invoke blocks the calling thread until the UI thread updates, so you won't gain anything. (Of course, if all the invoke calls are coming from the UI thread anyway, you won't lose anything either.)
      singulars
      1. POUI Dispatch Buffering?
      1. USGreg D
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload