getting late responsive time during retrieve data from db to php web page

[Genelia]

Hi,

I am creating php webpage for my filemaker application. I am getting problem in retrieve data from DB , it is taking so much time to retrieve and sometimes its going to deadlock condition.

 

I got to know the reason that due to huge no. of fields (around 5000), in my table, it is taking so much response time.

 

1 suggestion i got that i have to use 1 alternate table where number of fields will be less for retrieve purpose.

 

Please anybody give me suggestions for sort out my problem..

 

Thanks in advance,

 

[gpicard1]

If you are accessing layouts with lots of fields on them in your php or FM scripts, it will slow it down.  Creating special layouts with ONLY the necessary fields for a script to work will speed things up.

[Rick Whitelaw]

Why would there ever be 5000 fields in a single table? I ask because I want to know.

[Lee Smith]

Fields? 5000 Records with the field? 

[webko]

5000 fields would indicate that there may be a design issue as well - even my 'best' legacy system only has 2200 fields...

 

And, always use a layout with only the fields you need for your PHP queries - the queries will always bring back all the available information from the specified layout.

 

Cheers

Webko

[Genelia]

Yes fields are 5000. i am using 1 layout where necessary fields are there. but still during retrieval, it takes so much time as i get to know before retrieval PHP store all fields of DB in 1 variable and thast why it is taking time.

[Lee Smith]

Wow, 5000 fields on one layout. How do you digest what is there?

 

Your Profile shows you are Certified in version 10, is that correct?

 

Maybe if you explained what purpose these fields are for, we can get our heads around design. 

[Genelia]

No No, not all the 5000 fields are using on 1 layout. In DB i have 5000 fields but on layout we have required fields only.

 

but during retrieval from DB to PHP page taking time.

[webko]

before retrieval PHP store all fields of DB

 

It shouldn't. It should only get the data from the fields on the specified layout for use.

[IdealData]

Is the data coming from unstored calculation fields, or possibly summaries?

 

Still, we don't know how many fields are on the layout - how many are there?

[Genelia]

Yes, we have lots of calculation fields that we need to show.on our layout we have 100-125 fields

[IdealData]

That sounds a lot. Start experimenting by reducing the fields to see if the performance improves.

[webko]

There is no way you should have a web page that displays that much data at once, unless it is a Details page, which should only return the data for one record...