DataTables / DataTables/SearchPanes
Performances improvments with serverSide: true
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
It does seem that the search panes are rebuild for each request when serverSide is used.
Would it be possible to optionally avoid this ?
For example, panes may not be rebuild if there is no searchPanes[options] in the response (indicating that previous one can still be used), a new option could allow to use only the data in the first request, or there could be something like a hash returned by the server and panes could only be rebuild when this hash change.
This would help performances a lot when there is a lot of options :)
Thanks a lot and have a nice day,
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by tracing the serverSide request lifecycle and the response handling for searchPanes[options] to find where panes are rebuilt; first establish the intended reuse or invalidation rule, then define tests showing when panes are retained and when they are rebuilt.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100