Comment 18 for bug 514808

18m of Python time - on the server ???? meaning more or less 100% CPU usage ???? with normal priority ????

also the number of queries - and hence the load on the optimizer - seems to high

May be a solution is to build a distinct view which returns the columns to print explicitly (translated name instead of id...), which is called once per account.- this will reduce the number of queries to some 100 (1 per account) and probably the load of python too.