Question on Jprobe and jtest
GeeThree
software?How about JTest?Have you used it?what are your thoughts?I need
to do some procurement and was researching several code optimization
software.Most importantly what are the negatives?
Sorry for the number of questions.I did not want to post this on CH
because of my popularity on the board lately.
TIA.
prope//er
expedite the investigation of memory leaks and slow code.
Advantages:
-------------------
[*] The learning curve for JProbe is steep. It needs a really good
understanding of Java basics.
[*] The person conducting JProbe analysis needs to have an extremely
good understanding of the application they are debugging.
[*] JProbe is used in investigation so, it is not as if you push a
button and you know what is causing the problem. So it is important
that the developer identify the use-case that is causing the issue. The
whole investigation depends on knowledge of the usecase.
[*] Understand clearly how Garbage collection works.
[*] JProbe support is very responsive. They contact you within 3 hours.
Drawbacks:
----------------
[*] Learning Curve
[*] Weird Licensing Schemes. Enterprise Server vs Node Locked
prope//er
list certainly does not read like a list of advantages.
GeeThree
prope//er
GeeThree
Thanks for your response.I did go ahead and submit my PCR to the
purchasing dept for jprobe and Jtest.I had some issues at work for the
past ten days.Now that everything is resolved,we should have it in in a
couple of weeks.But the lisencing terms were pretty wierd.
prope//er
As an FYI, the agreement for license maintenance is different from the
licenses for the products. Just thought I would let you know. In the
interest of time, if you have a handful of users, then go for
node-locked which is a huge pain. The license server is good if you
have 50/60 people using JProbe. You purchase whats known as a
concurrent license. This means at any given point in time, there cannot
be more than x number of JProbe instances on desktop.
As you launch JProbe on desktop, it talks to a license server.
later
//
prope//er
be more than x number of JProbe instances on desktop. "
Should have read...
his means at any given point in time, there cannot
be more than x number of JProbe instances launched on the desktops in
the network.
GeeThree
thanks once again for the pointers. you know what bothers me most with
these IBM products? Their lack of uniformity when it comes to going
from one version to another. For ex, I am currently working on an
upgrade project from one version of a document management system to
another version of the SAME product. I do agree that there are a lot of
improvements in the later versions but these people did not carry these
enhancements through to the database level.
Now this DMS has several additions in their current version to the
previous versions. One significant change is a column in the underlying
database which was previously a FIELD stored in the database which
acted as the PRIMARY key for the table [with millions and millions of
rows] and hence INDEXED very efficiently. All was well. Right?
Now, when they move to the next version, they change this column to a
URL based PID which is 96 characters long. This URL [concatenation of
several columns in the database, hence COMPOSITE INDEX] SHOULD be
extremely efficient in retrieval because it has the server name and the
EXACT location of the ITEM embedded in it. But they made a HUGEEEEEEEE
blunder. They forgot[???????????] to include the concatenated columns
in the INDEX. And this PID is also not stored in the database. Now the
freakin retrieval is slow as HELL and I have a PMR open for this is a
MAJOR code change and I now have to figure out how in the world am I
gonna release this to all my clients..
GeeThree
the number of developers SPREAD out for us.