Here are my results monitoring the CPU usage for different configurations:
The counterpart for testing (PC) was connected to the WLAN router via Ethernet cable (100MB) all the time. Achieved net data rates for transfering a 10MB test file was roughly 450..500kByte/sec in average for all configs. Here are the top contributors: SBox connected via LAN and SMB -> 20% (smbd) Sbox connected via LAN and scp -> 33% (dropbear) SBox connected via WiFi link and SMB -> 35% (20% smbd + 15% wlan_main_servi) Sbox connected via WiFi link and scp -> 65% (dropbear + wlan_main_servi + 8% sirq_tasklet ) The astonishing load contributors during transfer in all cases: 15% caused by jive, jive_alsa and IRQ-7 ! (these processes consume below 1% in idle state) It looks like jive interupts in some way and slows down the file transfer. First I thought of on-demand scanning issues of the activated built-in server when storing to the USB-HDD. But scp transfers into /tmp cause similar CPU load activities of jive. Shutting down the built-in server doesn't make a difference, too. I've got no clue what's going on. Anyway, CPU load seems to be just part of the game and not the limiting bottleneck: Total CPU load for SMB via LAN was < 35%, which means the SB Touch CPU might support 3X the current transfer rate (-> 1.5MBtype/sec). Toby -- streumix ------------------------------------------------------------------------ streumix's Profile: http://forums.slimdevices.com/member.php?userid=39267 View this thread: http://forums.slimdevices.com/showthread.php?t=80707 _______________________________________________ Touch mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/touch
