IDES Installation: Slow import Abap

[Former Member]

Hi,

My installation of IDES on Maxdb 7.6.0.3 has been so slow, I installed a DB GUI to check the database and found that the database still have empty data volumes, but the import ABAP job seems not to be moving again: it has 2 jobs running and 1 waiting(for the past 24 hours).

How do I confirm whether installation has not got problems?

Thanks.

Bryne

[Former Member]

...hmmmm this is getting to technical for small me, but i understand the cache side, I just check and the cache size is 92800 (for both data cache and converter) is this enough?

And how do i go about the vectorIO simulation?

Thanks

[Former Member]

@Lars well if he(you) must, here you go:

SERVERDB: OJU

ID UKT Win TASK APPL Current Timeout Region Wait

tid type pid state priority cnt try item

T5 6 0xD8 Pager Vvectorio 0 0 2359232(s)

T6 6 0xD8 Pager Vvectorio 0 0 2359232(s)

T7 6 0xD8 Pager Vvectorio 0 0 2359232(s)

T8 6 0xD8 Pager Vvectorio 0 0 2359232(s)

T9 6 0xD8 Pager Vvectorio 0 0 2359232(s)

T10 6 0xD8 Pager Vvectorio 0 0 2359232(s)

T11 6 0xD8 Pager Vvectorio 0 0 2359232(s)

T12 6 0xD8 Pager Vvectorio 0 0 2359232(s)

T13 6 0xD8 Pager Vvectorio 0 0 2359232(s)

T14 6 0xD8 Pager Vvectorio 0 0 2359232(s)

T15 6 0xD8 Pager Vvectorio 0 0 2359232(s)

T16 6 0xD8 Pager Vvectorio 0 0 2359232(s)

T17 6 0xD8 Pager Vvectorio 0 0 2359232(s)

T18 6 0xD8 Pager Vvectorio 0 0 2359232(s)

T19 6 0xD8 Pager Vvectorio 0 0 2359232(s)

T20 6 0xD8 Pager Vvectorio 0 0 2359232(s)

T21 6 0xD8 Pager Vvectorio 0 0 2359232(s)

T22 6 0xD8 Pager Vvectorio 0 0 2359232(s)

T23 6 0xD8 Pager Vvectorio 0 0 2359232(s)

T24 6 0xD8 Pager Vvectorio 0 0 2359232(s)

T25 6 0xD8 Pager Vvectorio 0 0 2359232(s)

T26 6 0xD8 Pager Vvectorio 0 0 2359232(s)

T27 6 0xD8 Pager Vvectorio 0 0 2359232(s)

T28 6 0xD8 Pager Vvectorio 0 0 2359232(s)

T29 6 0xD8 Pager Vvectorio 0 0 2359232(s)

T30 6 0xD8 Pager Vvectorio 0 0 2359232(s)

T31 6 0xD8 Pager Vvectorio 0 0 2359232(s)

T32 6 0xD8 Pager Vvectorio 0 0 2359232(s)

T33 6 0xD8 Pager Vvectorio 0 0 2359232(s)

T34 6 0xD8 Pager Vvectorio 0 0 2359232(s)

T35 6 0xD8 Pager Vvectorio 0 0 2359232(s)

T36 6 0xD8 Pager Vvectorio 0 0 2359232(s)

T42 7 0x668 User 2520 Runnable 0 0 37850 33254334(r)

T113 4 0x578 Savepnt Vsuspend (253) 0 0 1780064(s)

T137 5 0x7EC GarbCol IO Wait (R) 0 133 12 194(r)

Console command finished (2011-05-26 07:29:55).

[lbreddemann]

Well, if this is happening all the time, I'd check:

- the cache size (if it's very small you'll see savepoints all the time)

- the SimulateVectorIO parmeter. If this is not set to NEVER, then vector IO is not happening and this makes stuff really slow.

Also, I'd propose to set the number of GarbageCollectors to something like number of CPUs or so, to allow at least a little parallelity for these.

regards,

Lars

[markus_doehr2]

> Well, if this is happening all the time, I'd check:

> - the cache size (if it's very small you'll see savepoints all the time)

There will be savepoints after each table creation is finished unless one specifies "-force_repeat" during the data load. Setting that parameter decreased the installation time by factors since eventually all data loading will be serialized because each R3load triggers savepoint after savepoint, even on empty tables.

> - the SimulateVectorIO parmeter. If this is not set to NEVER, then vector IO is not happening and this makes stuff really slow.

In our system this is set to "NEVER" but I see VectorIO all the time

Hmmm...

Markus

[lbreddemann]

> Well, if this is happening all the time, I'd check:
> > - the cache size (if it's very small you'll see savepoints all the time)
> 
> There will be savepoints after each table creation is finished unless one specifies "-force_repeat" during the data load. Setting that parameter decreased the installation time by factors since eventually all data loading will be serialized because each R3load triggers savepoint after savepoint, even on empty tables.

correct!

> > - the SimulateVectorIO parmeter. If this is not set to NEVER, then vector IO is not happening and this makes stuff really slow.
> 
> In our system this is set to "NEVER" but I see VectorIO all the time 

Don't misunderstand me here.

The suspend reason will be the same regardless of the parameter value.

The parameter just decides what vectorIO-API is used. If NEVER is chosen, the OS-API is used which usually means, that real vector IO is done (and rather quickly).

When the parameter is not set to NEVER, an internal API is used, that actually simulates vectorIO by performing multiple singleIOs. And this would take a lot more time than the 'real' vectorIO.

regards,

Lars

[Former Member]

Thanks Markus,

I have ran the command and I can see a lot of activities going on.

[lbreddemann]

I bet Markus wanted to see the actual output...:-)

[markus_doehr2]

> My installation of IDES on Maxdb 7.6.0.3 has been so slow, I installed a DB GUI to check the database and found that the database still have empty data volumes, but the import ABAP job seems not to be moving again: it has 2 jobs running and 1 waiting(for the past 24 hours).

> How do I confirm whether installation has not got problems?

run

x_cons <SID> sh ac 1

if you see activity it's still running.

If you don't have enough memory configured for the database cache to hold the biggest tables (e. g. D010TAB) index creation will take a long time, especially on 7.6.

Markus