Re: [cx-oracle-users] Arraysize dependent on run time?

[Shai B. <sh...@pl...>]

Hi Moritz,

Two notions come to mind:

1) Are you sure the time is wasted in Python-land? Do you have a way to 
measure the execution of the query without Python or cx_Oracle being invoved 
(e.g. in SQL*Plus)?

2) Assuming it is -- I've seen delays on the order of seconds show up when you 
create a lot of circular references -- the Python GC gets invoked then and can 
cause surprisingly large "lapses". You can check the documentation of the 
stdlib's gc module for ways to verify and/or eliminate this issue.

HTH,
	Shai.

On Tuesday 23 August 2016 18:43:26 Moritz Liebelt wrote:
> Hi,
> 
> I fetch rows form an Oracle Locator DB with web.py and cx_Oracle! I use the
> unreleased version of cx_Oracle! Furthermore I read the sdo_geometry
> objects in the sql-statement and build a json based on this.
> 
> For a 500m-Tile with 4634 rows I need 0,326 (measured time in the browser=
> waiting time (DB + Webserver))
> For a 500m-Tile with 5081 rows I need 10,1 second???
> You can see an overview
>   *500m-Tile_A ( 2311 rows)* *500m-Tile_B (3799 rows)* *400m-Tile (4137
> rows)* *500m-Tile_E (4634 rows)* *500m-Tile_C (5081 rows)* *500m-Tile _D
> (6241 rows)*
> *sdo_geometry (cx_Oracle)* 0,18s 0,26s 0,27s 0,326s 10,1s 13,77s
> *Size* 729KB 1,2 MB 1,3 MB 1,4MB 1,6 MB 2 MB
> 
> Is there anywhere a Threshold? Because the time is increasing and I do not
> understand why.
> It does not refer to Browser problems. I think that this is depending on
> the webserver.
> 
> Does someone knows this issue?