Samba and Application Response Measurement (ARM 4.0)

David Collier-Brown davecb at sun.com
Sun Mar 16 15:34:23 GMT 2008


The best idea was Volker's,to look at the profiling calls, as 
those are the ones the team uses internally fo performance work.

--dave

Sven Kubiak wrote:
> Well, i found the profile.c, profiles.c and status_profile.c. But i don't
> know if these are the right files to begin with.
> 
> As with the callers of (sys_)read, could you name the files to start with.
> It's difficult to figure out how and where calls are made.
> 
> Thanks and best regards
> Sven
> 
> Am 10.03.08 23:40 schrieb "Volker Lendecke" unter
> <Volker.Lendecke at SerNet.DE>:
> 
> 
>>On Mon, Mar 10, 2008 at 06:30:14PM -0400, David Collier-Brown wrote:
>>
>>> You're starting with some fairly hard stuff.  It's
>>>easier to find the callers of (sys_)read, for example,
>>>in recvfile.
>>>
>>> For a simple server transaction, it starts with a read
>>>of the socket, which gets a request from the client.
>>>The first write to the same socket ends the latency
>>>period, and the last write before a read ends the transfer.
>>>period.  The time between the last write and the next read
>>>the think time of the client user of system.
>>>
>>> Once you've done the really coarse measurement, you can
>>>drill down to the detailed requests, which will begin
>>>with the decoding of a request packet (or and_x) and
>>>end with the last reply.
>>
>>Well, there's always the PROFILE stuff that measures each
>>and every single SMB, along with the trans2 subtransactions
>>and so on. Why don't you build upon those?
>>
>>Volker
> 
> 
> 

-- 
David Collier-Brown            | Always do right. This will gratify
Sun Microsystems, Toronto      | some people and astonish the rest
davecb at sun.com                 |                      -- Mark Twain
(905) 943-1983, cell: (647) 833-9377, home off: (416) 223-5943 
(800) 555-9786 x56583, bridge: (877) 385-4099 code: 506 9191#


More information about the samba-technical mailing list