David Crossley wrote:
Ron Blaschke wrote:
Second, I am investigating how to tell Forrest that index.html and
/index.html really are the same thing.
That is still a problem, for any absolute link
e.g. /samples/faq.html
We have a workaround for the Forrest site-author site:
Ron Blaschke wrote:
Second, I am investigating how to tell Forrest that index.html and
/index.html really are the same thing.
That is still a problem, for any absolute link
e.g. /samples/faq.html
We have a workaround for the Forrest site-author site:
David Crossley wrote:
Ron Blaschke wrote:
Ron Blaschke wrote:
I've started to look at things, and were able to look at the Cocoon
profiler things with forrest run in site-author/.
Here's a short, edited, sample:
body-index.html
NN Components(Role)Average time
David Crossley wrote:
David Crossley wrote:
Ron Blaschke wrote:
Ron Blaschke wrote:
[snip]
NN Components(Role)Average time Lastest times
1 file ([1]) 213 ms 30 ms30 ms 581 ms
2 idgen 6 ms 10 ms 0 ms10 ms
3 xinclude
Ron Blaschke wrote:
David Crossley wrote:
David Crossley wrote:
Ron Blaschke wrote:
Ron Blaschke wrote:
[snip]
NN Components(Role)Average time Lastest times
1 file ([1]) 213 ms 30 ms30 ms 581 ms
2 idgen 6 ms 10 ms
David Crossley wrote:
Ron Blaschke wrote:
Ron Blaschke wrote:
I've started to look at things, and were able to look at the Cocoon
profiler things with forrest run in site-author/.
Here's a short, edited, sample:
body-index.html
NN Components(Role)Average time
Ron Blaschke wrote:
David Crossley wrote:
Ron Blaschke wrote:
David Crossley wrote:
I've started to look at things, and were able to look at the Cocoon
profiler things with forrest run in site-author/. Quite a number of
things were already present within Forrest, but required some
Monday, August 29, 2005, 5:21:07 PM, David Crossley wrote:
Ron Blaschke wrote:
David Crossley wrote:
Currently, I am wondering about three things:
- How can the top level pipes be replaced with their profiling
counterparts, without too much hassle?
Perhaps this is possible using an
Friday, August 26, 2005, 9:23:38 AM, David Crossley wrote:
Ron Blaschke wrote:
[snip profiler stuff]
Some Forrest developers definitely want to see these
numbers and do want to get their hands dirty with Cocoon.
There must be a lot that we can do to speed it up, e.g.
tune our cache; more
Ron Blaschke wrote:
David Crossley wrote:
Ron Blaschke wrote:
[snip profiler stuff]
Some Forrest developers definitely want to see these
numbers and do want to get their hands dirty with Cocoon.
There must be a lot that we can do to speed it up, e.g.
tune our cache; more efficient
Sunday, August 28, 2005, 5:55:07 PM, Ron Blaschke wrote:
Sunday, August 28, 2005, 2:37:03 PM, David Crossley wrote:
Ron Blaschke wrote:
David Crossley wrote:
I've started to look at things, and were able to look at the Cocoon
profiler things with forrest run in site-author/.
Here's a short,
Ron Blaschke wrote:
There are two things I'd like to mention here. First, usually a
profiler at this low level (the VM) uses the JVMPI or JVMTI, and is
integreated via -Xrun... or -agentlib:... VM options, which I usually
simply set via forrest.jvmargs.
Helpful scripts would be good if a
Monday, August 22, 2005, 12:57:34 PM, David Crossley wrote:
Diwaker Gupta wrote:
So here's what I have right now:
o I can do a simple ./build.sh jar.debug -- this creates a debug version
of
Forrest. When you next run Forrest, the data will be automatically logged.
Where and how and
On Sunday 21 August 2005 10:11 pm, David Crossley wrote:
We cannot create a dependency on an LGPL library.
The terms go beyond those of the Apache License.
Forrest doesn't need to depend on JRat. Its only a tool for profiling. Is
there no provision for including optional code under a different
Diwaker Gupta wrote:
David Crossley wrote:
We cannot create a dependency on an LGPL library.
The terms go beyond those of the Apache License.
Forrest doesn't need to depend on JRat. Its only a tool for profiling. Is
there no provision for including optional code under a different
On 8/22/05, David Crossley [EMAIL PROTECTED] wrote:
Diwaker Gupta wrote:
So here's what I have right now:
o I can do a simple ./build.sh jar.debug -- this creates a debug version
of
Forrest. When you next run Forrest, the data will be automatically logged.
Where and how and what to
Greetings everyone,
Ron has done some excellent work on profiling Forrest (see [1], [2]). Since
then I've been looking at how can we integrate profiling into Forrest's build
process. My requirements were:
o open source (not necessarily, but preferable)
o good integration with our build process
17 matches
Mail list logo
