Hi All ,
Thakyou for the reply..actually the real problem was,after the grid
was created,we were using a query to fetch the latest record from the
database.That query was again traversing 1 lakh records and therefore it
was taking time.After replacing the query
with latest_record=db.table1.
Can we also see what event_pretty does?
On Friday, 22 February 2013 04:15:11 UTC-6, newbie wrote:
>
> I cross-verified and got the same result , timings is 32.00 ms for count
> query.Anyways, please find below the model and controller code:
>
> Model:
>
> db.define_table('table1',
>Field('dev
ok. how many "devices" and "users" are there ? maybe the time is spent
formatting references back to their "nice" format.
PS: can you post here the complete list of timings as returned by
response.toolbar() ?
On Friday, February 22, 2013 11:15:11 AM UTC+1, newbie wrote:
>
> I cross-verified and
I cross-verified and got the same result , timings is 32.00 ms for count
query.Anyways, please find below the model and controller code:
Model:
db.define_table('table1',
Field('device', type="reference devices", ondelete="SET NULL"),
Field('type', 'integer'),
Field('message', 'string', r
if SQLite takes 32 ms to count 10^5 records, than I'm impressed (or, more
likely, astonished) with its performance (but I remain dubious that you're
reading the correct timings).
Seems that the database is not the issue. Can we see the model for that
table ?
On Friday, February 22, 2013 10:07:3
I mentioned wrong data for the query which SQLFORM.grid is executed so
sorry for that, basically that query is taking 0.00 ms and below query has
taken 32.00 ms:
SELECT count(*) FROM table1 WHERE (table1.id > 0);
On Fri, Feb 22, 2013 at 2:24 PM, Niphlod wrote:
> wonderful. thanks.
> @newbie:
wonderful. thanks.
@newbie: can you see how many seconds it takes the query that has a count()
in it ? that one is probably taking more than a few millisec.
PS: SQlite starts to be kinda not the preferred way to store 10^5 records.
--
---
You received this message because you are subscribed
Hi Niphlod,
On 22/02/13 08:33, Niphlod wrote:
PS: I may be old enough to miss some new-style definitions, but what is
precisely " 1 lakh records" ?
100k - see http://en.wikipedia.org/wiki/Lakh
--
Regards,
PhilK
'a bell is a cup...until it is struck'
--
---
You received this message b
32 ms means 0.0032 seconds. Database is not the issue.
PS: I may be old enough to miss some new-style definitions, but what is
precisely " 1 lakh records" ?
On Friday, February 22, 2013 8:16:43 AM UTC+1, newbie wrote:
>
> Thanks for your prompt response.
> I am using sqlite database.I placed {{=r
Thanks for your prompt response.
I am using sqlite database.I placed {{=response.toolbar()}} in view and
found that, query which is being used in SQLFORM.grid is taking more time
than others.
Please find below the query and time taken to execute:
SELECT table1.device, table1.user, table1.type, t
what is your database engine?
we need to see if the bottleneck is in database side.
Place a {{=response.toolbar()}} in your view and paste here the generated
SQL and timings.
Are you using pagination? how many per page? even with 100.000 records, the
grid should use an offset to limit the loaded
Hi ,
i am a newbie in Web2pyI have more than 1 lakh records in database
table1 and i am displaying that table through an SQLFORM.grid.The problem
is the corresponding WebPage for this table1 is taking more than 15 seconds
to open.Is there a way we can solve this performance issue??.
12 matches
Mail list logo
