Re: [luau] Redstar3

2003-03-14 Thread Jimen Ching
On Fri, 14 Mar 2003, Charles Lockhart wrote: >written in Java. We're using sockets for the more primitive and limited >interfaces, we're using the ORBit CORBA stuff and the java CORBA stuff >for the more advanced interfaces. I'm curious as to how you decided to use ORBit. At my work place, we ar

Re: [luau] Redstar3

2003-03-14 Thread Ray Strode
Ok, probably nobody cares, but the group I work for/with has pretty much finished our first iteration of the Redstar3 array controller. An array in this case is an infrared ccd. The system is the main controller for imaging for astronomy. I mention it only because it's running Linux. Very

Re: [luau] memory and writes to disk - linux behavior question

2003-03-14 Thread Vince Hoang
On Fri, Mar 14, 2003 at 10:28:43AM -1000, Jeff Wong wrote: > This is normal. As far as linux is concerned, free memory is > wasted memory. If there is alot of unused memory linux will > automatically grab it for disk/file buffering and will keep it > until some other process requests a memory alloc

Re: [luau] memory and writes to disk - linux behavior question

2003-03-14 Thread Jeff Wong
On Fri, 14 Mar 2003, Charles Lockhart wrote: > Any ideas as to what may be going on? Is top lying, am I > misinterpreting the value that top is showing, is all the memory getting > mapped to the process even though it may not be completely used? > > -Charles > This is normal. As far as linu

Re: [luau] memory and writes to disk - linux behavior question

2003-03-14 Thread Charles Lockhart
Ok, I lied. For some reason I thought most of the memory was free when we first power up the system, but it comes up with about 200MB used. Seems like a lot, but I don't see anything hogging it all, so maybe it's just allocating memory really freely to the processes that are there. When first

Re: [luau] Redstar3

2003-03-14 Thread Charles Lockhart
Well, maybe. The primary reason I bring the Redstar3 up here is because there have been several times over the last year when I've gotten good feedback when stuck on some aspect of the system design or implementation, and I feel the Luau made a definite and positive contribution. I thank you

Re: [luau] memory and writes to disk - linux behavior question

2003-03-14 Thread Vince Hoang
On Fri, Mar 14, 2003 at 07:54:01AM +, Charles Lockhart wrote: > Then the application starts doing disk writes. It's streaming > imaging data to disk at sustained rates as high as 30MBPS. I'm > running top to get an idea of what's going on, and I watch the > free memory sink to about 3MB of data

Re: [luau] Redstar3

2003-03-14 Thread R. Scott Belford
On Thursday 13 March 2003 10:03 pm, Charles Lockhart wrote: > > Is that interesting? Probably not. Probably so. Thanks for the info. Very interesting. scott > > -Charles > > ___ > LUAU mailing list > [EMAIL PROTECTED] > http://videl.ics.hawaii.edu

Re: [luau] memory and writes to disk - linux behavior question

2003-03-14 Thread R. Scott Belford
On Thursday 13 March 2003 09:54 pm, Charles Lockhart wrote: > > Any ideas as to what may be going on? Is top lying, am I > misinterpreting the value that top is showing, is all the memory getting > mapped to the process even though it may not be completely used? > I have observed on a few of our

[luau] Redstar3

2003-03-14 Thread Charles Lockhart
Ok, probably nobody cares, but the group I work for/with has pretty much finished our first iteration of the Redstar3 array controller. An array in this case is an infrared ccd. The system is the main controller for imaging for astronomy. I mention it only because it's running Linux. It has

[luau] mlockall?

2003-03-14 Thread Charles Lockhart
Anybody use mlockall? If so, what effects did it have on you application performance? Your system performance? What have you heard about it? Thanks, -Charles

[luau] memory and writes to disk - linux behavior question

2003-03-14 Thread Charles Lockhart
I have a "dedicated system" (what do you call a system that's obviously not embedded but is designed (destined?) for a very narrow scope of operation?), a Compaq DL360 G1 box whose sole purpose in this existence is to run an application we have. The system's got 512 MB main memory. When we fi