plsqldoc very slow

elepak · Jan 8, 2007

I try to generate the documentation for a large package header (~100 procedure declarations).
The computation time for generating a header documentation seems highly dependant on the number of other documentation files present in documentation directory.

Example:
No other file - some milliseconds
3 table docs additional present - > 2 min
more html present - break by task manager

Effect is present even for smaller package headers (2 procedure declarations) - but not so dramatic.

Search cross references is set to none.

Using
pl/sql dev v 7.0.3
plsqldoc 1.2.0
against
Oracle 9iR2
with Oracle 9iR2 client

Any suggestions ?

Marco Kalter · Jan 8, 2007

That seems very slow to me. Is the documentation stored on a local drive or on a network share?

elepak · Jan 9, 2007

Yes its very slow

And (unfortunally) its a local drive.
And its tested on different computers.
Last one:
dual core - 2GHz - 2GB main memory

elepak · Jan 17, 2007

Problem still persist.
With this performance not really usable.

Bye the way - a real integrated (and thus enhanced) documentation functionality would be a real useful extension.

Butch Wesley · Mar 2, 2007

I am experiencing the same thing. I let a script to generate plsqldoc's for all our packages(144) and package bodies run overnight. It made it through about 80 of them in 12 hours. I'm using a 1.7ghz 768mb RAM writing to a local drive.

By the time I started generating plsqldoc for the packages I had already run it for our tables, views, functions, and procedures. These all ran quickly(approx 160 files generated). If I empty the directory of all the html files the packages script will run quicker at first but gradually slows down.

*edit

I was mistaken, I had not generated the tables yet. I ran the script for the tables and it generated plsqldoc for 250 tables very quickly. I then tried to generate the plsqldoc for the following package:

create or replace package plsqldoc_test is

function myfunc(p_vc1 varchar2, p_int number)return boolean;

end plsqldoc_test;

create or replace package body plsqldoc_test is
--This is the body of a package used to test the output of plsqldoc
--%app Test

--This function returns a boolean and takes in a varchar2 and integer
-- %usage This function is used as a test to see how well it works
-- inside a development environment.
-- %param p_vc1 This is a varchar2
-- %param p_int This is a number
-- %return returns a boolean that means nothing since this is a test
-- program
-- %raises
function myfunc(p_vc1 varchar2, p_int number)return boolean
is
begin
null;
end;

end plsqldoc_test;

And it took 2 minutes and 41 seconds. If I empty the directory(472 files)it takes less than a second to generate for the same code.

Thorsten Kohl (IBS) · Jun 11, 2007

Are there any news about this problem?
I've got the same problem. To document a few packages is no problem, when then the time which is needed becomes more and more.
I used it before 1 year without any performance problems. The differences are:
Old: Oracle 9.2
New: Oracle 10.2
Old: PlSqlDeveloper 7.02
New: PlSqlDeveloper 7.11

Example for the needed time. In sum there will be around 100 packages, but I can't document them

Verzeichnis von C:\DB_Documentation\11.05

28.04.2003 00:00 2.991 plsqldoc.css
28.03.2005 00:00 213 frame_home.html
26.09.2005 16:08 508 frame.html
11.06.2007 17:39 272 plsqldoc.ini
11.06.2007 17:40 12.144 Akqa_Fahrzeug.body.html
11.06.2007 17:40 14.098 akqc_sp.body.html
11.06.2007 17:40 37.430 Akqd_Aktion.body.html
11.06.2007 17:41 15.475 AKQD_CHECKER.body.html
11.06.2007 17:41 16.965 AKQD_DYNINSP.body.html
11.06.2007 17:42 5.951 akqd_erfident.body.html
11.06.2007 17:44 20.846 akqd_extpena.body.html
11.06.2007 17:44 10.663 AKQD_JOB.body.html
11.06.2007 17:45 23.183 Akqd_Parts.body.html
11.06.2007 17:47 16.916 AKQD_PRINT.body.html
11.06.2007 17:48 26.142 AKQD_RECHTE.body.html
11.06.2007 17:50 29.390 akqd_userpwd.body.html
11.06.2007 17:51 11.188 akqd_userwrite.body.html
11.06.2007 17:51 3.933 akqd_util.body.html
11.06.2007 17:57 57.073 akqg_sp.body.html
11.06.2007 18:03 28.832 Akqt_Sp.body.html
11.06.2007 18:05 10.259 AKQT_SP_SPEC.body.html
11.06.2007 18:19 .
11.06.2007 18:19 ..
11.06.2007 18:19 69.161 akqv_parser.body.html
11.06.2007 18:19 4.387 index.html
11.06.2007 18:19 3.960 frame_index.html

elepak · Jun 12, 2007

Problem is persistent - from my point of view.
NO change - no new informations.
We have about 50 packages in one of our projects (some of them very large)
and it is mostly impossible to generate a sufficient documentation using the plsqldoc plugin.

Thorsten Kohl (IBS) · Jun 12, 2007

I found a way to generate docs - not very nice but it works:

1) before starting PLSQLDeveloper create a new empty directory.
2) after starting PLSQLDeveloper set this empty dir as plsqldoc dir
3) open windows explorer (or whatever you are using) an go to this still empty dir
4) mark your packages in PLSQLDeveloper-tree and select generate documentation
5) when a new file is generated move it to another directory (this where you have generated docs for all other objects)
6) after doc generation has finished switch plsqldoc dir to the old one and use in configuration of plsqldoc "rebuild index"

You'll see how fast generation of docs could be...

elepak · Jun 12, 2007

But what happens to cross references/hyperlinks when you go this way ?

Thorsten Kohl (IBS) · Jun 12, 2007

I've just checked it and they're not generated. Only internal references are created.
That's bad

(but I think a doc without external links is better than no doc

)

Saheem · Jun 12, 2007

I have downloaded this plugin today for testing and i have the same issue too. Is there any reason as to why the documentation generates so slowly? especially since it was using about half of my cpu, and the files generated are not that big either (approx 3kb to 10kb each).

Thorsten Kohl (IBS) · Jun 12, 2007

I've tested now also the old version of PLSQLDeveloper, but it's the same problem.
Before around 1 year I generated the last docs without any problems. So I tested it also with the same old database => but without any change, the problem is still there.

Could it be, that the problem is caused by WinXP updates?

Saheem · Jun 13, 2007

i attempted to generate a very large amount of objects in one go and it got slower and slower. Then i recieved an "out of memory" error for some of the objects which i tried to generate documents for. But then it picked up pace again. Still not to the speeds i'd expect (1 object every 5 seconds).

Any ideas why this happening yet?

Saheem · Jun 20, 2007

Apologies for re-posting on this subject but i just wanted to ask if this issue was something being looked at or not?

Thorsten Kohl (IBS) · Jun 20, 2007

I hope that Allround Automations is looking for that problem. But to keep silent is not what I'm expecting...

elepak · Jun 20, 2007

I hope so - too

Maxnet · Aug 8, 2007

I use this command script for generating my documentation.
Before use this script you should move cmd.exe to the command.com to temporary fix the bug described in: http://www.allroundautomations.com/ubb/ultimatebb.php?ubb=get_topic;f=3;t=002485#000000 (if you do not do it, the HOST COPY command does not work correctly)
And script:

Code:

plugin plsqldoc DELETE;
plugin plsqldoc generate pkg_web_public ;
HOST MOVE D:\Projects\dosug.oracle\Documents\plsqldoc\PKG_WEB_PUBLIC.html D:\Projects\dosug.oracle\Documents\temp\
plugin plsqldoc generate  pkg_web_search;
HOST MOVE D:\Projects\dosug.oracle\Documents\plsqldoc\PKG_WEB_search.html D:\Projects\dosug.oracle\Documents\temp\
plugin plsqldoc generate pkg_languages;
.....
HOST MOVE D:\Projects\dosug.oracle\Documents\temp\*.* D:\Projects\dosug.oracle\Documents\plsqldoc\
plugin plsqldoc REBUILD;

Saheem · Sep 25, 2007

could you please elaborate a bit further on the above and also how it effects the performance issue of plsqldoc?

ehimmelreich · Sep 26, 2008

the batch file (run from command-line in windows)

Code:

"C:\Program Files\PLSQL Developer\plsqldev.exe" userid=scott/tiger@db commandfile=plsqldoc.pdc

the command file (run in plsql developer plsqldoc.pdc)

Code:

plugin plsqldoc DELETE;
plugin plsqldoc generate PKG1;
HOST MOVE "C:\Program Files\PLSQL Developer\plsqldoc\PKG1.*" C:\plsqldoc_temp\;
plugin plsqldoc generate PKG2;
HOST MOVE "C:\Program Files\PLSQL Developer\plsqldoc\PKG2.*" C:\plsqldoc_temp\;
plugin plsqldoc generate PKG3;
HOST MOVE "C:\Program Files\PLSQL Developer\plsqldoc\PKG3.*" C:\plsqldoc_temp\;
...
...
HOST MOVE C:\plsqldoc_temp\*.* "C:\Program Files\PLSQL Developer\plsqldoc\";
plugin plsqldoc rebuild;

this works for me quite well

Raimund Kelterer · May 13, 2009

I am running 7.1.5.1397 on XP SP2 and I have the same poor performance of plsqldoc. the workaround (host cmd /c "") with moving the generated html files to a temporary directory and move them back before 'rebuild' works fine. but this solution is quite long-winded.

are there any news ?

Marco Kalter · May 13, 2009

It is most likely a file system related issue. We're still looking into this.

plsqldoc very slow

Member

Administrator

Member

Member

Member

Member²

Member

Member²

Member

Member²

Member²

Member²

Member²

Member²

Member²

Member

Member

Member²

Member

Member²

Administrator

Similar threads