[evlatests] Missing Modcomp-Free data

[Mike Revnell]

One CMIB is more computer than all the Modcomps put together. This makes 
me suspect that no matter how fast the processor it would suffer the 
same fate. As I understand it the vispipe does most of its I/O as busy-wait.

Bryan Butler wrote:
> fine - but when i hear statements that vispipe runs at 99% CPU i get worried, 
> and think that the option of a bigger processor should be considered.
>
> 	-bryan
>
>
> On 6/12/07 14:02, Ken Sowinski wrote:
>   
>> On Tue, 12 Jun 2007, Bryan Butler wrote:
>>
>>     
>>> we do have the option of replacing the processor for vispipe, don't 
>>> we?  i
>>> vaguely recall that we could upgrade it to the equivalent of one of 
>>> the CMIB
>>> processors pretty trivially.  maybe it's time to look at that.
>>>       
>> I understand it to be exactly a cmib processor such as the
>> ones we are using today.  There is no problem with vispipe.
>> Rather we are learning about interactions between the executor,
>> correlator, idcaf, vis-pipe and subarrays.  The way to fix the
>> problem is to understand the interactions and render them
>> harmless; not to look for bigger processors.
>>     
> _______________________________________________
> evlatests mailing list
> evlatests at listmgr.cv.nrao.edu
> http://listmgr.cv.nrao.edu/mailman/listinfo/evlatests
>
>