timing out

Re[2]: timing out



Hi Scott,

As Bruce and Claudiu said, the easiest way is to increase the timeout, but
you should look at your code for any inefficencies - On a decent machine,
compiled mivascripts can handle some 1000-2000 updates/second (straight in a
loop, without lookups to other dbs), so there shouldn't be any reason that
your script takes more than the default 90seconds.

Filters, if not used properly, can be very slow (look at Ivo's website for
tips how to use them more efficiently), mainly because they scan the entire
database everytime you apply the filter. An index and MvFIND would be much
more efficient.

Another way that I use quite often when I don't want to create another index
is to use arrays or structures (arrays if your primary ID or search criteria
is an integer, otherwise a structure). You then create the array by looping
through the entire database, collect the values. You do the same for your
lookup table, and when the IDs match, merge them (or write the matching
value into the first structure).

The you loop again through the first db and write back the (changed) values.
How this actually works depends of course on your app, but essentially you
can update relatively large tables with 2 loops and no filters (or
additional indices) at all. And again, reading/writing a few thousand
records doesn't take very long.

HTH,

Markus

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf
Of IDS
Sent: Sunday, April 17, 2005 1:25 PM
To: [email protected]
Subject: Re[2]: [meu] timing out

Hello Bruce,

claudiu helped me solve it. I just had to increase the global time out.

I am using a filter. I am wondering if an index would be more efficient
though? This app is really a utility updating data content. No records are
added or deleted thru this process.

Thanks,

Scott
IDS

Sunday, April 17, 2005, 10:0 0:04 AM, you wrote:

BGPc> Can you improve the throughput by using either an index or a
BGPc> filter. 3000 records shouldn't really timeout unless you are doing
BGPc> this on a palm pilot<G>.

BGPc> -Bruce

>> -----Original Message-----
>> From: [email protected]
>> [mailto:[email protected]] On Behalf Of IDS
>> Sent: Sunday, April 17, 2005 1:44 AM
>> To: [email protected]
>> Subject: [meu] timing out
>>
>> Hello,
>>
>> just looking for some thoughts on why my app would be timing out in
>> Mia sifting through 3000+ records.
>>
>> I reading from 3 dbs, and writing to only 2, record by record, rec
>> #1
>> thru EOF.
>>
>> But, the app keeps timing out. I have only two eval statements where
>> only one actually gets printed based on condition.
>>
>> I'm only getting through just less than 50% of the db.
>>
>> What else I'm doing, the db's are open thru the whole loop
>> (MvWhile). Updating only one field in the record and it's a fixed
>> value -- hardcoded.
>>
>> TIA for any ideas.
>>
>> --
>> Best regards,
>> IDS mailto:[email protected]
>>
>>

Re[2]: timing out



Hello Bruce,

claudiu helped me solve it. I just had to increase the global time out.

I am using a filter. I am wondering if an index would be more efficient
though? This app is really a utility updating data content. No records
are added or deleted thru this process.

Thanks,

Scott
IDS

Sunday, April 17, 2005, 10:0 0:04 AM, you wrote:

BGPc> Can you improve the throughput by using either an index or a filter. 3000
BGPc> records shouldn't really timeout unless you are doing this on a palm
BGPc> pilot<G>.

BGPc> -Bruce

>> -----Original Message-----
>> From: [email protected]
>> [mailto:[email protected]] On Behalf Of IDS
>> Sent: Sunday, April 17, 2005 1:44 AM
>> To: [email protected]
>> Subject: [meu] timing out
>>
>> Hello,
>>
>> just looking for some thoughts on why my app would be timing out in
>> Mia sifting through 3000+ records.
>>
>> I reading from 3 dbs, and writing to only 2, record by
>> record, rec #1
>> thru EOF.
>>
>> But, the app keeps timing out. I have only two eval statements where
>> only one actually gets printed based on condition.
>>
>> I'm only getting through just less than 50% of the db.
>>
>> What else I'm doing, the db's are open thru the whole loop
>> (MvWhile). Updating only one field in the record and it's a fixed
>> value -- hardcoded.
>>
>> TIA for any ideas.
>>
>> --
>> Best regards,
>> IDS mailto:[email protected]
>>
>>

timing out



Can you improve the throughput by using either an index or a filter. 3000
records shouldn't really timeout unless you are doing this on a palm
pilot<G>.

-Bruce

> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of IDS
> Sent: Sunday, April 17, 2005 1:44 AM
> To: [email protected]
> Subject: [meu] timing out
>
> Hello,
>
> just looking for some thoughts on why my app would be timing out in
> Mia sifting through 3000+ records.
>
> I reading from 3 dbs, and writing to only 2, record by
> record, rec #1
> thru EOF.
>
> But, the app keeps timing out. I have only two eval statements where
> only one actually gets printed based on condition.
>
> I'm only getting through just less than 50% of the db.
>
> What else I'm doing, the db's are open thru the whole loop
> (MvWhile). Updating only one field in the record and it's a fixed
> value -- hardcoded.
>
> TIA for any ideas.
>
> --
> Best regards,
> IDS mailto:[email protected]
>
>

timing out



hi,

You should make the timeout bigger to your mia global timeout (it is 30 by
default)..But generally you have a normal timeout from your browser .. so
one of the common ways is to use refresh meta from 500 records to 500..

best regards,
claudiu

-----Original Message-----
From: [email protected] [mailto:[email protected]]On
Behalf Of IDS
Sent: dimanche 17 avril 2005 10:44
To: [email protected]
Subject: [meu] timing out


Hello,

just looking for some thoughts on why my app would be timing out in
Mia sifting through 3000+ records.

I reading from 3 dbs, and writing to only 2, record by record, rec #1
thru EOF.

But, the app keeps timing out. I have only two eval statements where
only one actually gets printed based on condition.

I'm only getting through just less than 50% of the db.

What else I'm doing, the db's are open thru the whole loop
(MvWhile). Updating only one field in the record and it's a fixed
value -- hardcoded.

TIA for any ideas.

--
Best regards,
IDS mailto:[email protected]

Hello,

just looking for some thoughts on why my app would be timing out in
Mia sifting through 3000+ records.

I reading from 3 dbs, and writing to only 2, record by record, rec #1
thru EOF.

But, the app keeps timing out. I have only two eval statements where
only one actually gets printed based on condition.

I'm only getting through just less than 50% of the db.

What else I'm doing, the db's are open thru the whole loop
(MvWhile). Updating only one field in the record and it's a fixed
value -- hardcoded.

TIA for any ideas.

--
Best regards,
IDS mailto:[email protected]