Difference: AMC13DebugLog (151 vs. 152)

Revision 15212 Feb 2016 - DanielGastler

Line: 1 to 1
Please log AMC13 test activity below, blog style (new entries at top)

2016-02-12, dgastler

It turns out that cms1 is not very fast and is the bottleneck for these speed tests.

Dominique instructed me on how to get the FEROL to drop the data when it lands and now the CPU use has dropped dramatically and the throughput went way up.

Here are the commands to throw away the data:

>lspci -v
        02:03.0 Memory controller: CMS DAQ group Device fea0 (rev 01)
        Flags: 66MHz, slow devsel
        Memory at dd210000 (32-bit, non-prefetchable) [size=64K]
        Memory at dd200000 (32-bit, non-prefetchable) [size=64K]
>sudo busybox devmem 0xdd210000 32 0

With 1952 Byte events, I was able to max out the AMC13's random event rate at 130kHz.

To try to max out the link, I increased the event size until I got backpressure. This happened at FAKE_DATA_SIZE of 0x40 (6560bytes) with a max rate of about 75kHz.

This gives a throughput of 500MBps, which is what we would expect.


2016-02-10, dgastler

Stressing the FEROL with data from an amc13 with no writing to disk.
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback