My members will have the ability to customize their profile page with X-X widgets, each widget will have different data Like list music, those people have the following list.
Many widgets include: - The list of uploaded media - the list of people they are following - List of the following people - HTML / text widget - Media statistics (number downloads etc.) ) - Comments for other members to leave comments widget
Some widgets have to return data, as there can be hundreds of results.
I have not done so many DBs working to return all these data for any optimization right now ... What would be the most effective way to recover data ... what would be per widget Will 1 DB call be acceptable? There may be about 5-20 widgets per page.
If you want more information about my situation, please feel free to ask.
Paul
Because you completely excluded your work in widgets Each widget will be used to do a single query for all the necessary functionality. This is also the case, even if you have recovered the widget through AJX (which CPP noted is not a bad idea).
Secondly, I will install some mechanism for each widget to register my widget, after all the widgets have been registered, I will set a single query in which all widget questions will be included. Technically it has a one-time FAQ but in a round-trip, see Multitratoria and Multi Queries in NH Reference).
Also do not forget that lazy loads are hidden DB retractions and you may have a large display effect, in such a case using lazy loads, where an eager load is appropriate (for example, fu. The name of the bar where you always show the bar. The value of the name when you present the FU unit)
Decrease in performance may also decrease that calls 20-30 requests per request, , Questions S, depending on the size and complexity of shape as well as data sets with filters.
Comments
Post a Comment