Any way to change blob size -- do I need to?

Question

I'm tinkering around with remote blob storage in my dev environment -- doing a lot of different options to see how it really works.  One thing I noticed is that when I dragged a file to a document library and it got stored under my filestream filename
in the file system (instead of the mdf file of the provider database) that files it created seemed to be about 61k.  So if I dragged a 5 MB PDF file, there would be about 85 of these small blob files.  That seemed to be a little small and inefficient
to me, so I thought I could do something to increase the file size of the blob files and reduce the number of them.  I tried to increase the filestreammaxsizeinlineblob parameter of the RBS.MSI installation from 61140 to 102400 (and I tried doing this
in a number of different ways that I don't want to count).  When I did that, nothing seemed to end up in the file system.  Then I started poking around in the database and saw the table mssqlrbs_filestream_data_1.rbs_filestream_data_1 and saw the
blob_size column and nothing was larger than 65641.  So it seems that no data is being stored in the file system when I mandate a filestreammaxsizeinlineblob parameter of 102400 and that makes sense now looking at the aforementioned table because everything
was formed at a much lower size then the threshold I instituted.  My two questions are this:  1) is there any way to increase the blob_size so it's larger and there are less files on the file system or is that something hardcoded into sharepoint,
and 2) is the 61 - 64k size just fine and what appear to be lots of files to me is really nothing for the server to handle?  Frankly, the performance I got was quite good retreiving documents from BLOBs in my test environment, but was wondering what would
happen when it got actual use in production and tons of these files are floating around on the file system.
*This is a different issue than setting the minimumblobstoragesize in powershell -- I know how to do that*

Answer 1

1) Yes you can.
2) It's fine, don't bother changing it.
The thing you're seeing at work is called Shredded storage. It effectively allows SharePoint and SQL to only store updates to large files. Part of this involves shredding files to smaller chunks so it can identify which bits have changed. Because you're
externalising BLOBs you see these shredded files on the disk.
RBS is no longer anywhere near as useful in 2013 as it used to be and for the majority of cases i'd advise against using it. It might actually be causing worse performance as you take a small but measurable hit whenever you use an externalised BLOB, which
is fine for large slow files but very counter productive for small bits of data that are best kept in the database.
Thanks for the quick response, Alex!  If you have time, could you please briefly reply as to why RBS isn't as useful in 2013 (my setup is SP2013 SP1 w/ SQL2012 SP1), and what would be the threshold where it *would* be useful (i.e. number of files in document
storage DB, total document storage size, etc.)