Comment 2 for bug 715444

i tried also with cadaver - most response times around 10 seconds -
I see very heavy database access
I have a structure with m:n - typically a multiple of 10 (1:10) on each level of the levels - the deepest level has 290 records in total - so this is not a very important number

the first level is a recursive tree ( stock.location )

I confirm - not usable in production (and daunting at demos)