With a USB3.0 stick u get the Maximum out of your USB 2.0 interface.
And this is more then most of Sd-Cards do.
Indeed, and most USB2 sticks do not even come close to the limits of a standard USB2 port, such as the RPi has.
But a good USB3 stick will allow the USB2 port to be used to the maximum capacity of the RPi.
And with some sensible overclocking, that capacity itself can be raised a bit higher.
And i think the more important point is that while u overclock there may occur errors on your sd-card.
this is not happening with an USB stick.
To be perfectly clear, it's only USB3 sticks that are useful for RasPlex.
Many common USB2 sticks are even slower than class 4 SDcards, making it pointless to use them with an RPi.
Thats what i read the last 2 days. hope this is right so far
I agree with almost everything you said in your posts, though some clarification was in order.
There are also some additional measures I take to ensure best results, such as expanding the main storage partitions.
There's also some doubt about the best way to deal with "cmdline.txt", as some users report loss of SSH access.
Here is my own install procedure for best results:
1: Use RasPlex installer or "Win32 Disk Imager" twice, to install the RasPlex image both on the SDcard and the USB3 stick.
2: Use the free edition of "Paragon Partition Manager" to expand the Ext4 partition (2nd partition) to fill out the unused area.
NB: This is important only for the USB3 stick, but I do it for the SDcard as well, just in case I later decide to use it stand-alone (which also requires re-editing its "cmdline.txt".) Expanding the USB3 partition might be unnecessary for a small Plex library, but for a large one it really is important, and in any case it would be pointless to leave 14GB of a 16GB stick completely unusable for RasPlex cache storage.
3: Edit the "cmdline.txt" file of both SDcard and USB3 stick to contain the following line:
boot=/dev/sda1 disk=/dev/sda2 ssh quiet oprofile.timer=1
NB: Having the same command line both on SDcard and USB3 stick ensures consistent behaviour for all hard and soft reboot methods.
4: If you want overclocking you can add the following near the end of your "config.txt" files like I do (again for BOTH devices).
arm_freq=950
core_freq=450
sdram_freq=450
over_voltage=4
As you can see by comparing these settings to the examples higher up in that file, I've chosen to go 50 MHz lower than the maximum frequencies shown in those examples, and 2 steps lower with the overvoltage level. Going higher would increase the risk of damage and I don't think the speed gain it would give is worth that risk.
Also, if your RPi is enclosed by some small cupboard or other unventilated container, then you should not overclock at all.
My own RPi has a standard RPi cover (with ventilation slits) and is sitting behind my TV set on top of a Netgear switch, but with air access on the other 5 sides, and it has no heat problems. It's been running 24/7 for quite a while now, so I think I would have noticed such problems by now.
Btw: If anyone thinks it would be useful to quote any part of this post elsewhere, you are free to do so.
Best regards: dlanor