FWIW: The bigger picture... Or why I have been asking a lot of questions lately...

[Bruce Labitt]

Joshua Judson Rosen wrote:
> Bruce Labitt <bruce.labitt at myfairpoint.net> writes:
>   
>> What I'm trying to do:  Optimizer for a radar power spectral density problem
>>
>> Problem:  FFTs required in optimization loop take too long on current 
>> workstation for the optimizer to even be viable. 
>>
>> Attempted solution:  FFT engine on remote server to reduce overall 
>> execution time
>>
>> Builds client - server app implementing above solution.  Server uses 
>> OpenMP and FFTW to exploit all cores.
>>     
> [...]
>   
>> Implements better binary packing unpacking in code.  Stuff works
>>
>> Nit in solution:  TCP transport time >> FFT execution time, rendering 
>> attempted solution non-viable
>>
>> Researches TCP optimization: Reads countless papers on tcp optimization 
>> techniques... Fails to find a robust solutions or methodology for 
>> problem.  Tries most techniques written in papers, only realizing a 10% 
>> gain.  Not good enough.  Still needs to be faster
>>
>> Driven to more exotic techniques to reduce transport time.  Explores 
>> parallel sockets, other techniques
>>     
> [...]
>   
>> Hey, that is my bigger picture...  Any and all suggestions are 
>> appreciated.  Undoubtedly, a few dumb questions will follow.  I appear 
>> to be good at it.  :P  Maybe this context will help list subscribers 
>> frame their answers if they have any, or ask insightful questions.
>>     
>
> Where exactly does NFS fit into this?
>
>   
NFS is used for the file system for the server.  The 1Gb link is used 
for both NFS and the data transport.  The data being transfered to the 
server never exists as a file so there is no hit for writing/reading 
to/from file.