Re: Peformance questions

Hi,

Thanks for the prompt reply. While in some sense sleeping is not a performance issue per-se, if it spends 85% of it's time sleeping
while the app waits, it's at least a perceived performance issue. But that's just nit-picking.

The suggestion:
   
> you should disable DFS with jcifs.smb.client.dfs.disabled

had a remarkable effect. The time waiting for peekKey() went down to 20% of total time, and total time dropped by 75% from 5min30 to
1min17m. The total time in SmbWrite dropped from 7secs to 2sec.

So...this leads to two more questions:

Q3: is there any disadvantage in disabling DFS permanently?

Q4: in general terms, if this were a Windows or Linux setup, how would you go about working out what was wrong with having DFS
enabled? FWIW, I can run a packet sniffer on a Linux server if that helps.


Thanks again!



On 26/02/2013 4:24 AM, Michael B Allen wrote:
> It sounds like there's some kind of networking quirk like a socket
> option that's wrong for the Android JVM. This almost certainly has
> little or nothing to do with JCIFS. It's not a "performance" issue.
> The methods that you reference are just sleeping. Although there could
> easily be something timing out like a DFS referral that isn't
> applicable because you're not in a domain environment in which case
> you should disable DFS with jcifs.smb.client.dfs.disabled = false.
> Otherwise, I'm not familiar with Android development so I have no idea
> as to how to go about debugging such a thing.
>
> Mike
>