How to manage huge data?? JSP.

azliza

How to display huge data as 300 000 records faster. Below is the example of the query that i used to display the data and by default 10 records per page. Anyone can help me to improve the time displaying the result. It take so long to display those data.

select *
from ra_call_leakage
where service_number is not null and data_status='0'
order by created_date DESC limit 10 offset 0

TQ

dino

1. pertama skali optimize table;

optimize table ra_call_leakage

2. Add index..

ALTER TABLE ra_call_leakage  ADD INDEX(service_number,data_status);

3. remove * dkt from tue.... guna value yg btul2 guna utk dipaparkan kat skrin...
cth;

select service_number from ra_call_leakage
where service_number is not null and data_status='0'
order by created_date DESC limit 10 offset 0

sblm try catit dulu masa proses skript sblm lakukan step nih...

azliza

ok tq

actually my query is like below, but still slow when display..so how to improve this...

select service_number,cdr_batch_num,(end_time - seize_time)as call_duration,dialed_digits,
to_char(created_date,'DD/MM/YYYY HH24:MI:SS')as created_date, f_get_leakage_name(leakage_code)as leakage_code,
to_char(seize_time,'DD/MM/YYYY HH24:MI:SS')as seize_time, to_char(end_time,'DD/MM/YYYY HH24:MI:SS')as end_time,
round(charge,2) as charge,r_data4,status,charge_differences, r_data1,
round(subid) as subid ,user_id,batch_date,record_src,is_action_taken,date_delete,delete_category, is_leakage,
data_status,f_get_calltype_name(call_type)as call_type ,f_get_direction_name(direction)as direction,
f_get_cdrtype_name(cdr_type)as cdr_type, imsi
from ra_call_leakage
where service_number is not null and data_status='0'
order by created_date DESC limit 10 offset 0

dino

mak aaii
pendpt aku buang seme yg ade kaitan ngan calculation tue.... (jika aku tak slh la)... biar simple...

azliza

ok i will try buang some of the field and see how.

azliza

alahai terhantar dua kali plak...dah edit...he

[ Last edited by  azliza at 27-6-2007 10:11 AM ]

shahnazz

ni macam telco punya data ni.

data retrieval should be fast sebab takde link atau join tables. kalau rows dah dekat 300,000 memang la expected to be slow. kelembapan mungkin kepada network or workload to the database. ni run script from client side or server side?

kalau data tak guna as real-time (as and when needed) elok dump je table tu to some other table or database away from the database server. dari situ u boleh bega-bega the data locally. tak tau kalau kaedah ni sesuai bagi u.


p.s. still kat SAL lagi ke?

azliza

script tu run dkt client side...setiap kali nak sort atau cari data dia akan call server ...
tp slow sgtt ...



ohh syanazz ingat lagi yee .... ohh sy di SAL part time jer ....

azliza

script tu run dkt client side...setiap kali nak sort atau cari data dia akan call server ...
tp slow sgtt ...



ohh syanazz ingat lagi yee .... ohh sy di SAL part time jer ....