Can we display around 100000 rows using React-Table by consuming Json data via API?
I have a requirement to consume huge volume of data ( like more than 100000 rows) by calling API end point and Data format is JSON and display them in react page. I am developing the logic using React-Table, but would like to hear experts opinion to know whether this is possible in reactjs? Is React-Table the right option in reactjs? Will there be performance issues?
reactjs
add a comment |
I have a requirement to consume huge volume of data ( like more than 100000 rows) by calling API end point and Data format is JSON and display them in react page. I am developing the logic using React-Table, but would like to hear experts opinion to know whether this is possible in reactjs? Is React-Table the right option in reactjs? Will there be performance issues?
reactjs
Why display them all at once? Paging?
– Magnus
Dec 27 at 14:27
1
He could display all items for a variety of reasons, all of which are not subject of the answer
– Mosè Raguzzini
Dec 27 at 15:26
add a comment |
I have a requirement to consume huge volume of data ( like more than 100000 rows) by calling API end point and Data format is JSON and display them in react page. I am developing the logic using React-Table, but would like to hear experts opinion to know whether this is possible in reactjs? Is React-Table the right option in reactjs? Will there be performance issues?
reactjs
I have a requirement to consume huge volume of data ( like more than 100000 rows) by calling API end point and Data format is JSON and display them in react page. I am developing the logic using React-Table, but would like to hear experts opinion to know whether this is possible in reactjs? Is React-Table the right option in reactjs? Will there be performance issues?
reactjs
reactjs
asked Dec 27 at 14:24
prathap K
91
91
Why display them all at once? Paging?
– Magnus
Dec 27 at 14:27
1
He could display all items for a variety of reasons, all of which are not subject of the answer
– Mosè Raguzzini
Dec 27 at 15:26
add a comment |
Why display them all at once? Paging?
– Magnus
Dec 27 at 14:27
1
He could display all items for a variety of reasons, all of which are not subject of the answer
– Mosè Raguzzini
Dec 27 at 15:26
Why display them all at once? Paging?
– Magnus
Dec 27 at 14:27
Why display them all at once? Paging?
– Magnus
Dec 27 at 14:27
1
1
He could display all items for a variety of reasons, all of which are not subject of the answer
– Mosè Raguzzini
Dec 27 at 15:26
He could display all items for a variety of reasons, all of which are not subject of the answer
– Mosè Raguzzini
Dec 27 at 15:26
add a comment |
1 Answer
1
active
oldest
votes
Yes this is surely possible but involves the usage of virtual views like react-virtualized
The problem with 100k rows is that first render takes a lot of time, scroll could be tedious and every re-render takes a significant amount of time too.
With virtual views data is rendered only in active viewport and element are added/removed upon scroll reducing the rendering/reconciliation payload.
ok. Thanks Mose. I will explore this option. Right now I have used react-table and pagination and tested with 2000 rows , look good. will try to explore with higher volumes using react-table too and post the results.
– prathap K
Dec 28 at 7:33
If you encounter some sort of bottleneck, this article is really useful: sumologic.com/blog/code/react-table-alternatives
– Mosè Raguzzini
Dec 28 at 8:58
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53946583%2fcan-we-display-around-100000-rows-using-react-table-by-consuming-json-data-via-a%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Yes this is surely possible but involves the usage of virtual views like react-virtualized
The problem with 100k rows is that first render takes a lot of time, scroll could be tedious and every re-render takes a significant amount of time too.
With virtual views data is rendered only in active viewport and element are added/removed upon scroll reducing the rendering/reconciliation payload.
ok. Thanks Mose. I will explore this option. Right now I have used react-table and pagination and tested with 2000 rows , look good. will try to explore with higher volumes using react-table too and post the results.
– prathap K
Dec 28 at 7:33
If you encounter some sort of bottleneck, this article is really useful: sumologic.com/blog/code/react-table-alternatives
– Mosè Raguzzini
Dec 28 at 8:58
add a comment |
Yes this is surely possible but involves the usage of virtual views like react-virtualized
The problem with 100k rows is that first render takes a lot of time, scroll could be tedious and every re-render takes a significant amount of time too.
With virtual views data is rendered only in active viewport and element are added/removed upon scroll reducing the rendering/reconciliation payload.
ok. Thanks Mose. I will explore this option. Right now I have used react-table and pagination and tested with 2000 rows , look good. will try to explore with higher volumes using react-table too and post the results.
– prathap K
Dec 28 at 7:33
If you encounter some sort of bottleneck, this article is really useful: sumologic.com/blog/code/react-table-alternatives
– Mosè Raguzzini
Dec 28 at 8:58
add a comment |
Yes this is surely possible but involves the usage of virtual views like react-virtualized
The problem with 100k rows is that first render takes a lot of time, scroll could be tedious and every re-render takes a significant amount of time too.
With virtual views data is rendered only in active viewport and element are added/removed upon scroll reducing the rendering/reconciliation payload.
Yes this is surely possible but involves the usage of virtual views like react-virtualized
The problem with 100k rows is that first render takes a lot of time, scroll could be tedious and every re-render takes a significant amount of time too.
With virtual views data is rendered only in active viewport and element are added/removed upon scroll reducing the rendering/reconciliation payload.
answered Dec 27 at 15:25
Mosè Raguzzini
2,9601020
2,9601020
ok. Thanks Mose. I will explore this option. Right now I have used react-table and pagination and tested with 2000 rows , look good. will try to explore with higher volumes using react-table too and post the results.
– prathap K
Dec 28 at 7:33
If you encounter some sort of bottleneck, this article is really useful: sumologic.com/blog/code/react-table-alternatives
– Mosè Raguzzini
Dec 28 at 8:58
add a comment |
ok. Thanks Mose. I will explore this option. Right now I have used react-table and pagination and tested with 2000 rows , look good. will try to explore with higher volumes using react-table too and post the results.
– prathap K
Dec 28 at 7:33
If you encounter some sort of bottleneck, this article is really useful: sumologic.com/blog/code/react-table-alternatives
– Mosè Raguzzini
Dec 28 at 8:58
ok. Thanks Mose. I will explore this option. Right now I have used react-table and pagination and tested with 2000 rows , look good. will try to explore with higher volumes using react-table too and post the results.
– prathap K
Dec 28 at 7:33
ok. Thanks Mose. I will explore this option. Right now I have used react-table and pagination and tested with 2000 rows , look good. will try to explore with higher volumes using react-table too and post the results.
– prathap K
Dec 28 at 7:33
If you encounter some sort of bottleneck, this article is really useful: sumologic.com/blog/code/react-table-alternatives
– Mosè Raguzzini
Dec 28 at 8:58
If you encounter some sort of bottleneck, this article is really useful: sumologic.com/blog/code/react-table-alternatives
– Mosè Raguzzini
Dec 28 at 8:58
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53946583%2fcan-we-display-around-100000-rows-using-react-table-by-consuming-json-data-via-a%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Why display them all at once? Paging?
– Magnus
Dec 27 at 14:27
1
He could display all items for a variety of reasons, all of which are not subject of the answer
– Mosè Raguzzini
Dec 27 at 15:26