[hardy] coriander performance issues

[Michael A. Phillips]

Binary package hint: linux-source-2.6.22

I use coriander for some astronomy purposes. Specifically I use a DMK 21AU04.AS (http://www.astronomycameras.com/en/p...o/dmk21au04as/) with a custom version of coriander 1.0.0.

My question is around the frames per second (FPS) performance while running on laptop battery power. Running on A/C, I can use the camera to receive, display and save up to 60fps. Running my Lenovo T60p on battery power I can reliably only get 15fps. Running at either 30 or 60fps the performance drops nearly in half. That is at 60fps I get 30-40 fps etc..

I've tuned my Hardy install using kpowersave to turn the cpu scaling full up. The default in the BIOS will not allow this, but you can over ride it. Without turning the CPU to 100% (both CPUs really, it's a dual core), you cannot get full performance at even 15fps. So that much is a success.

I heard from the individual that performed the customization that,

"...recent Fedora distros by default use the new "juju" firewire stack in the kernel which is not yet working properly with coriander..."

I don't know all what that means, but am struggling to understand and control what factors are preventing me from using this coriander at full performance while running my laptop on battery power.

If there is addiationl info that would help with this situation, please let me know and I will get as much as I can for you.

TIA,

Mike

[Andrew Straw (astraw)]

I don't see how this can be related to coriander. Coriander is an app built using the libdc1394 library, which is used to access firewire (IIDC 1394 DCAM) digital cameras. According the website you list, the model you have is a USB camera. Thus, I wouldn't think coriander could access the camera, nor would anything about firewire affect the camera.

[Michael A. Phillips (maphilli14)]

Oh, I am mistaken. I am in fact using the "F" model, not the "U" model. DMK21AF04 vs DMK21AU04.

http://www.astronomycameras.com/en/products/firewire-cameras/mono/dmk21af04as/

I assure you it is the Firewire model. I can attach some syslog output as soon as I get back in front of the camera.

Please tell me what other information you might find useful as I believe it could be related to the app, kernel or libraries?!

TIA,

Mike

[Michael A. Phillips (maphilli14)]

Some dmesg output from card/camera removal and reinsertion.

It's an AVerMedia 1394 CardBus adapter.

Mike

[Andrew Straw (astraw)]

My guess is that, since it appears to have nothing to do with CPU frequency, it may have to do with power. I would try powering the camera from independently from the computer and see if the computer running from battery is a red herring. Some cardbus adapters have DC power inputs that you could use, and some cameras also have a DC power in. If you could power either of those independently from the camera, you should have some more useful information.

Also, hardy is using the 2.6.24 kernel for what it's worth. But, I use firewire cameras extensively with desktop PCs and have never experienced the kind of issue you're describing. It might be useful to ask on the libdc1394 mailing list -- they are friendly and collectively have a lot of experience.

[Michael A. Phillips (maphilli14)]

I am trying the libdc1394 group. It's powered externally and not by the pcmcia. I've got a 12v DC transformer that plugs into the card to feed power to the camera via the bus, but not the PCMCIA itself.

Thanks for the help!

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Michele Mangili (mangilimic)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!