You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The next version of Mup should have a few benchmark tests (VMs) to check performance on different machines and different text options (simple, complex, small, large) to have a good indication as to the amount of text the parser can handle without having significant impact (potential UI freeze when used in a desktop application). The workaround in these cases would be to move processing to a background thread or use Task.Run(() => Parse(Text)) to perform the operation, however it would be useful to have an indicator when this could be the case.
The benchmark tests are mostly useful for desktop applications that would use the parser as web application back-ends are generally better in performance and there is no risk of UI freeze (unless you perform API calls in a synchronous fashion, but that's rather a problem with how the developer implements their desktop application than a problem with the parser itself, any API call can cause a UI freeze).
The text was updated successfully, but these errors were encountered:
The next version of Mup should have a few benchmark tests (VMs) to check performance on different machines and different text options (simple, complex, small, large) to have a good indication as to the amount of text the parser can handle without having significant impact (potential UI freeze when used in a desktop application). The workaround in these cases would be to move processing to a background thread or use
Task.Run(() => Parse(Text))
to perform the operation, however it would be useful to have an indicator when this could be the case.The benchmark tests are mostly useful for desktop applications that would use the parser as web application back-ends are generally better in performance and there is no risk of UI freeze (unless you perform API calls in a synchronous fashion, but that's rather a problem with how the developer implements their desktop application than a problem with the parser itself, any API call can cause a UI freeze).
The text was updated successfully, but these errors were encountered: