Skip to content

docs(performance): offloading to the server #162

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 5, 2020
Merged

docs(performance): offloading to the server #162

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion troubleshooting/general-issues.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -119,7 +119,7 @@ There are also certain measures a web app should take to improve its performance

* Loading content on demand (such as a cell value) should be done through a nested component and its `OnParemetersSetAsync` method. A similar example is available in the [load tooltip content on demand](https://github.com/telerik/blazor-ui/tree/master/tooltip/in-grid) and [load hierarchy data on demand](https://github.com/telerik/blazor-ui/tree/master/grid/load-on-demand-hierarchy) sample projects. You should not use an async method in a component's `Template` (or any `RenderFragment`) directly, because their execution is awaited by the framework before the fragment can render at all (`Templates` and `RenderFragment` instances are basically synchronous).


* If you need to generate documents or prepare some data, try to offload this task to the server. You can create an HTTP request and gather the processed information. With this approach, you will gain from the better server-side performance and won't download all the data on the client-side.


## See Also
Expand Down