The maximum BSON document size is 16 megabytes. — Source: MongoDB Docs
Here are the approximate English version word counts of some popular novels:
In March of 2013 I decided to build a new desktop for the sole purpose of running OSX. I’ve enjoyed getting my job done on a Macbook for several years and thought having a desktop version would just be dandy. Being a tinkerer, I couldn’t resist the challenge and flexibility of being able to boot into any OS of my choice. Parts were ordered and I started with Mavericks.
It worked fine until my first update. Not that the update broke anything but the anxiety of keeping up with updates while maintaining a 100% operational system was just too scary. After all, I do need to get work done. I nuked my install with Windows 8.1 and life was fine for a while. Dual 22″ screens, SSD, and kickass video card is just too dang useful in any OS, I can suffer along right?
I use various tools that give me a somewhat functional environment for my work (Cygwin, putty, etc.) but it never quite worked right if I had real work to do where I needed to send files, or copy/paste lines of code. At the end of the day, I was just more productive on OSX even with less screen real-estate.
‘Why didn’t you install Linux?’ Says just about anyone who knows me and my love for that OS, but at the end of the day, I need to do work. And that work involves doing demos and presentations using WebEx, GoToMeeting and various other tools that absolutely HATE Linux. Besides, I get my Linux fill with my server, which I will detail in a future post.
I went back to www.tonymacx86.com to see what progress had been made in the ‘Hackintosh’ world. I found that they had adopted the name ‘Customac’, which I immediately liked the sound of but haven’t fully adopted yet. I found that a new community developed custom BIOS for my board makes the OSX update process painless (no patching DSDT or manually editing plists after every update).
Thanks to the www.tonymacx86.com community for creating the tools that made this possible and honestly, quite painless.
Purchased recommended (for Mar 2013) hardware: http://www.gigabyte.com/products/product-page.aspx?pid=4279&dl=1#ov
Followed the guide for my motherboard: http://www.tonymacx86.com/bios-uefi/130888-bios-uefi-screenshots-gigabyte-z77x-up5-th.html
Installation instructions with Unibeast and El Capitan (Thanks company Macbook!): http://www.tonymacx86.com/el-capitan-desktop-guides/172672-unibeast-install-os-x-el-capitan-any-supported-intel-based-pc.html
Only scary part was opting to use a community bios since Gigabyte essentially abandoned a REALLY feature rich motherboard. Now I had Mavericks installed originally using the F11 version of the BIOS. But I did have issues with USB3 and Sound working after coming back from sleep. Not show stoppers just a hassle. I decided to try out this new F12j community bios which fixes all of those issues without DSDT patching. This makes applying OSX updates less of a potential headache as well.
Anything useful or interesting that I’ve done in the past few years has been posted to https://github.com/fullaware
According to this, a single port 10 GbE adapter needs (at minimum) to be placed in a server expansion slot that is a PCIe 1.0 x 8 (8 lane bus); a dual port adapter must go in a x16 slot if it is a PCIe 1.0 bus.
Any PCIe 2.0 expansion slot can handle a dual port 10 GbE adapter, since the slowest bus (x8) runs at 4,000 MB/s.
So, if you are providing a 10 GbE solution using older servers, check with the customer (or verify!) that they will have an open server expansion slot that is x8 or x16.
Bus speed requirements
Bus speed requirements are listed below:
· 4 Gb Fibre Channel requires 425 MB/sec
· 8 Gb Fibre Channel requires 850 MB/sec
· 10 GB Fibre Channel requires 1,250 MB/sec
Bus speeds in PCIe servers
|PCIeXpress 1.0 x 1||250|
|PCIeXpress 1.0 x 2||500|
|PCIeXpress 1.0 x 4||1,000|
|PCIeXpress 1.0 x 8||2,000|
|PCIeXpress 1.0 x 16||4, 000|
|PCIeXpress 1.0 x 32||8,000|
|PCIeXpress 2.0 x 8||4,000|
|PCIeXpress 2.0 x 16||8,000|
|PCIeXpress 2.0 x 32||16,000|
You are actually sorting the decimal value of the IP Address.
A2: IP Address
Tired of that expensive home lab going to waste keeping up with this whole “cloud” fad…and thus paying your mortgage? How about putting that computing power to something useful? Build your own Watson! After you’ve completed your “Lab-in-a-box” you will have the equivalent virtualized hardware to complete the Watson Jr cluster.
I have a machine booting ESXi 5.1 on Intel 520 180GB SSD. Then then running FreeNAS-8.3.0-RELEASE-x64 (r12701M) on a VM that I have configured the 4 local 1TB 7200 RPM SATA disks as RDMs. http://blog.davidwarburton.net/2010/10/25/rdm-mapping-of-local-sata-storage-for-esxi/
FreeNAS runs ZFS on the 4 x 1TB (rdm) drives. I added 32GB vmdk on the SSD is used by FreeNAS as a ZFS cache.
NFS export list mount process requires the name resolution of the client. When a client initiates the request for a NFS share, the servers checks its export list for the requested directory and name of the client in this access list for that particular share. Now if server fails to resolve the name of the initiator it denies its request for mounting that share. In order to overcome this problem you must have a dns server in network or else you have you manually enter the names and IP address information in to hosts file of the server.
That little bit of news was very helpful during this build as I had not been able to connect from the ESXi host to the FreeNAS VM running on that same host after much tinkering with permissions and network settings. Opened up the console on the FreeNAS VM, edited /etc/hosts to give the ESXi server IP a host name. BAM, NFS mounted with no problem.
new-alias grep findstr