1) param is called often several times (in auto/end etc)
2) The question is not about params, but about accessors speed at all.
If all acessors were XSAccessor for example (catalyst makes a lot of
calls -stack/action/dispatcher , etc internally during request), then
your overall speed would be
On 29 Apr 2010, at 10:06, Oleg Pronin wrote:
Maybe it is not the bottleneck, but how many places do we have
like this that are not a bottleneck ? maybe the sum of all these
mini mistakes is the bottleneck ?
Do the profiling, answer the maybe question.
- Mark
On 29/04/2010, at 7:06 PM, Oleg Pronin wrote:
[...]
Maybe it is not the bottleneck, but how many places do we have
like this that are not a bottleneck ? maybe the sum of all these
mini mistakes is the bottleneck ?
I've done some research on this topic, not from a computer science POV, but
Oleg Pronin wrote:
Maybe it is not the bottleneck, but how many places do we have
like this that are not a bottleneck ? maybe the sum of all these
mini mistakes is the bottleneck ?
NYTProf profile or it didn't happen :-)
Carl
___
List:
Carl Johnstone wrote:
NYTProf profile or it didn't happen :-)
Is there any best practices or hints page on how to use Catalyst and
NYTprof? I haven't used it before and I wonder if people include it
into a running catalyst application (and then periodically review
results in some way) or
I was kind of hoping this thread would get to more helpful issues. It
did, and thanks.
It's hard for us to profile a running application, for several reasons.
(1) there is a web server in the way, and (2) the storage requirements
(and to some extent performance) are a hit. Also, a management
* Oleg Pronin syber@gmail.com [2010-04-29 11:10]:
Maybe it is not the bottleneck, but how many places do we have
like this that are not a bottleneck ? maybe the sum of all
these mini mistakes is the bottleneck ?
Maybe, maybe, maybe. Stop guessing. Profile the code in question.
Here is my
Hey Catalyst / DBIC folks,
I am leaving my job and, thus, my position is becoming available!
The title is QA Tools Developer - you would be working on custom internal apps
at Riverbed Technology, a network acceleration company in downtown San
Francisco, CA. Good company, good people, good
