Improving performance of page in wicket 1.3
up vote
0
down vote
favorite
I am using wicket-1.3 in my application and a page is divided in 2 parts, 1st is having categorySelector wicket id which is shown dropdown and based on the dropdown value category wicket id will be changed by application. see below code
<div wicket:id="categorySelector" >Category selection controls</div>
<div wicket:id="category" >Category Data</div>
I have select 1 value from categorySelector dropdown value and category panel will show data in Propertylistview and data size is around 4k but its taking time around 4-5 minutes to page load.
I want to know why its taking too much time and is there any other alternative approach to implement the functionality for load huge data.
I have seen pagination concept also but i think it will not help me also.
java wicket wicket-1.5
asked Nov 14 at 8:19
Nitin
348
add a comment |
up vote
0
down vote
favorite
I am using wicket-1.3 in my application and a page is divided in 2 parts, 1st is having categorySelector wicket id which is shown dropdown and based on the dropdown value category wicket id will be changed by application. see below code
<div wicket:id="categorySelector" >Category selection controls</div>
<div wicket:id="category" >Category Data</div>
I have select 1 value from categorySelector dropdown value and category panel will show data in Propertylistview and data size is around 4k but its taking time around 4-5 minutes to page load.
I want to know why its taking too much time and is there any other alternative approach to implement the functionality for load huge data.
I have seen pagination concept also but i think it will not help me also.
java wicket wicket-1.5
asked Nov 14 at 8:19
Nitin
348
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am using wicket-1.3 in my application and a page is divided in 2 parts, 1st is having categorySelector wicket id which is shown dropdown and based on the dropdown value category wicket id will be changed by application. see below code
<div wicket:id="categorySelector" >Category selection controls</div>
<div wicket:id="category" >Category Data</div>
I have select 1 value from categorySelector dropdown value and category panel will show data in Propertylistview and data size is around 4k but its taking time around 4-5 minutes to page load.
I want to know why its taking too much time and is there any other alternative approach to implement the functionality for load huge data.
I have seen pagination concept also but i think it will not help me also.
java wicket wicket-1.5
asked Nov 14 at 8:19
Nitin
348
I am using wicket-1.3 in my application and a page is divided in 2 parts, 1st is having categorySelector wicket id which is shown dropdown and based on the dropdown value category wicket id will be changed by application. see below code
<div wicket:id="categorySelector" >Category selection controls</div>
<div wicket:id="category" >Category Data</div>
I have select 1 value from categorySelector dropdown value and category panel will show data in Propertylistview and data size is around 4k but its taking time around 4-5 minutes to page load.
I want to know why its taking too much time and is there any other alternative approach to implement the functionality for load huge data.
I have seen pagination concept also but i think it will not help me also.
java wicket wicket-1.5
java wicket wicket-1.5
asked Nov 14 at 8:19
Nitin
348
asked Nov 14 at 8:19
Nitin
348
asked Nov 14 at 8:19
Nitin
348
asked Nov 14 at 8:19
Nitin
348
asked Nov 14 at 8:19
Nitin
348
348
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
Pagination should help you because you will load only slices of the data, not everything at once.
In addition the browser will have less HTML elements to render!
answered Nov 14 at 8:35
martin-g
11.9k1825
let me implement this way functionality.
– Nitin
Nov 15 at 6:08
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
Pagination should help you because you will load only slices of the data, not everything at once.
In addition the browser will have less HTML elements to render!
answered Nov 14 at 8:35
martin-g
11.9k1825
let me implement this way functionality.
– Nitin
Nov 15 at 6:08
add a comment |
up vote
1
down vote
Pagination should help you because you will load only slices of the data, not everything at once.
In addition the browser will have less HTML elements to render!
answered Nov 14 at 8:35
martin-g
11.9k1825
let me implement this way functionality.
– Nitin
Nov 15 at 6:08
add a comment |
up vote
1
down vote
up vote
1
down vote
Pagination should help you because you will load only slices of the data, not everything at once.
In addition the browser will have less HTML elements to render!
answered Nov 14 at 8:35
martin-g
11.9k1825
Pagination should help you because you will load only slices of the data, not everything at once.
In addition the browser will have less HTML elements to render!
answered Nov 14 at 8:35
martin-g
11.9k1825
answered Nov 14 at 8:35
martin-g
11.9k1825
answered Nov 14 at 8:35
martin-g
11.9k1825
answered Nov 14 at 8:35
martin-g
11.9k1825
11.9k1825
let me implement this way functionality.
– Nitin
Nov 15 at 6:08
add a comment |
let me implement this way functionality.
– Nitin
Nov 15 at 6:08
let me implement this way functionality.
– Nitin
Nov 15 at 6:08
let me implement this way functionality.
– Nitin
Nov 15 at 6:08
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%2f53295710%2fimproving-performance-of-page-in-wicket-1-3%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
