[00:49] *** tabthorpe has quit IRC (Ping timeout: 258 seconds) [05:31] *** Nahual has joined #arpnetworks [05:55] *** nitemare has joined #arpnetworks [06:02] *** qbit1 has joined #arpnetworks [06:02] *** trobotham has quit IRC (*.net *.split) [06:02] *** qbit has quit IRC (*.net *.split) [06:02] *** mercutio has quit IRC (*.net *.split) [06:03] *** nitemare is now known as trobotham [06:11] *** qbit1 is now known as qbit [06:14] *** mercutio has joined #arpnetworks [06:14] *** orwell.freenode.net sets mode: +o mercutio [06:26] *** mercutio has quit IRC (*.net *.split) [06:26] *** mercutio has joined #arpnetworks [06:26] *** ChanServ sets mode: +o mercutio [06:27] *** tabthorpe has joined #arpnetworks [06:27] *** tabthorpe has quit IRC (Changing host) [06:27] *** tabthorpe has joined #arpnetworks [09:37] *** Nahual has quit IRC (Ping timeout: 240 seconds) [09:39] *** Nahual has joined #arpnetworks [10:16] *** ziyourenxiang has joined #arpnetworks [10:16] *** ziyourenxiang has quit IRC (Changing host) [10:16] *** ziyourenxiang has joined #arpnetworks [10:20] *** ziyourenxiang has quit IRC (Client Quit) [10:21] *** ziyourenxiang has joined #arpnetworks [10:22] Gotta be careful with an offer like that mike-burns. If you were sufficiently bloody-minded you *could* implement microsoft word in three lines of C. [11:13] *** ziyourenxiang has quit IRC (Quit: Leaving) [16:50] I don't really understand the difference between arp VPS and arp thunder...I expected the thunder server, which has 4x the RAM, SSD, and Sandy Bridge over Nehalem, to be faster for the same operations. But it's the opposite. [16:51] not quite sure what I expected, but I didn't expect the hardware to look identical to an arp vps on the thunder, though that's certainly convenient. [16:51] but then there's the obvious question of why does it sound like I'm getting a lot more for the same money with a thunder than a vps? [16:55] well, I'm not really doing a full apples-to-apples comparison yet, kernel, compiler, etc. versions are not yet in sync [16:55] nonetheless would love to hear more insights [17:05] Huh that does sound unusual. Thunder is intended to give dedicated (or better!) performance, particularly with disk IO. I haven't tried Thunder yet so I can't speak first-hand, but I am tentatively planning on migrating my company's Metal to Thunder. Your experience gives me some pause. [17:05] (Not that my migration would be instantaneous anyways - it would be setup, benchmark, etc before cutting-over) [17:06] casey: what is going worse in particular? [17:10] resurrecting a topic from above, i also ordered a second VPS and have no IP for it [17:10] put in a ticket early this morning, still waiting on a reply [17:10] boots up fine, just no networking connectivity [17:18] mercutio: compile time for gcc, etc. [17:19] perlgod: do you have an IP block already? [17:19] casey: that's interesting, maybe send in a ticket? [17:19] yeah, just a single IPv4 address for a metal server i also have [17:19] compile time is usually cpu related [17:19] mercutio: well like I said I'm still on inconsistent versions of stuff, so I'll get things in line first. [17:20] ah, [17:20] i have found clang is faster than gcc in the past [17:20] oh you were using gentoo [17:20] but what *is* thunder? Just the same as VPS on different hardware? [17:20] it's dedicated resources, so it should be more consistent performance wise [17:21] having slower cpu seems odd [17:21] logically the same software managing things? just a different config/pools of hardware underneath? [17:21] and I guess no overprovisioning of resources [17:21] yeah and no over provisioning of cpu cores. [17:21] err over subscribing [17:21] what about RAM, etc.? [17:22] ram is as it is for the plan [17:22] oh ram is never over subscribed [17:22] that'd suck :) [17:22] my first experience with VPS's was at vpslink.com, where we seriously overprovisioned everything to the max. Anyone who actually put any significant load on their VPS got reprovisioned onto a [17:22] "bad customers" server with all the other people who actually used resources [17:23] so they ended up having the most awful experience while the people who didn't actually do much got great performance. [17:23] heh [17:23] since, most money was being paid into the business by the latter group. pretty lousy business model, IMHO. [17:23] disk performance on everything is more consistent than it used to be [17:23] with the usage of shared storage. [17:24] and ime sluggish disk performance is one of the most frustrating issues to have with a vps [17:24] I haven't kept up, but inconsistent I/O has always been my biggest issue with VM's at places I've worked. [17:24] yeah, well shared storage makes it a lot better, as the load is spread out a lot more [17:25] last company had our database servers on self-managed vmware hardware - as a DBA that certainly made things "interesting"... :/ [17:25] so you'd need more heavy users at once to notice [17:25] they ended up provisioning dedicated storage when they switched to a new database platform, and thus no longer had a need for me, lol [17:26] I'll have to do some more comparisons in detail while I still have both services going. [17:27] but the Thunders seem like a much better deal than the regular VPS's, wondering what the catch is ;) [17:27] well the beginning prices start a little higher [17:28] but yeh i reckon the price point is good [17:29] HAS_A_BANANA: personally, I feel that while Thunder is a VERY compelling service offering for many, if your company is able to manage dedicated servers without issue then I'd stick with that. The advantage of Thunder is removing some administration overhead of getting servers all set up and configured for redundancy, etc. [17:29] with convenience comes some loss of flexibility/control [17:35] mercutio: ah, well I went from a $60/month VPS to a $90/monnth Thunder. For that 50% increase in cost I went from 4GB to 16GB RAM, 128GB to 400GB SATA, addition of 160GB SDD for 128 --> 560GB total storage, a newer/faster CPU generation, 6 --> 10TB bandwidth (don't care honestly)... [17:36] and it should have been $63/month as I had 4x CPU cores configured on the VPS [17:36] *** ziyourenxiang has joined #arpnetworks [17:36] cool [17:36] 16gb of ram for $90 hmm [17:36] that does seem good [17:37] the storage was nice too - now I can dump all my personal backups there too. [17:38] just once in a while, primary is a portable ssd [17:39] are there any hardware tiers behind the scenes? how is older hardware phased out? [17:40] one thing I was hoping for with this transition was to get better compilation times, mainly because building the Go application where I work and running unit tests on it takes about twice as long on the ARP VPS as my MacBook Pro [17:41] i wonder if the versions are doing something with that [17:43] the mac is great hardware, but I'd expect a highly-tuned and more modern linux system to be faster than Mac OS bloat [17:44] for our app it's easy enough to be consistent - we target a specific Go and PostgreSQL version. [17:45] let me just get the O/S consistent as a foundation first ;) [17:45] I'm still running off the boot CD kernel, and ARP's version of the Gentoo boot CD is from 2013!! [17:46] up_the_irons: could you add this to the dropdown selector, and/or allow a text input for pasting a custom URL to an ISO? http://distfiles.gentoo.org/releases/amd64/autobuilds/20170504/install-amd64-minimal-20170504.iso [17:47] i'd expect modern linux to be slower than old mac system with the same cpu [17:47] gcc keeps getting slower and slower [17:47] That's what she said!! [17:47] lolol, kernel 3.10.7 on the Thunder vs 4.11.0 on the VPS. :/ [17:48] kernel won't make much diff for compiling [17:48] gcc version is more likely to make a diff [17:48] yeah, I was comparing compiling the same version of GCC, but using different versions of GCC to do that compilation :| [17:49] GCC whatever-it-was also probably being 4 years out of date. [17:49] yeah that's probably not a good tet [17:49] test [17:49] as for Golang, newer versions compile faster, but I'm not sure if they have optimized more heavily for Mac [17:54] I should really throw them for a loop and put it on OpenBSD ;) [17:59] openbsd may not work on arp thunder by default [17:59] may or may not work [17:59] there was a bug in openbsd that required a workaround before. [17:59] but it's meant to be fixed in 6.1 [21:17] *** Nahual has quit IRC (Quit: Leaving.)