@ewwhite Once the underwriters settle down after the most recent shake-up and get used to the new regulations, it will get easier. Closings in Seattle used to be as short as 10 days. In 2010 they were 10 weeks just to close. It's down to 5 now.
When my Ex and I split, we were lucky enough that a local business owner had a fully-paid house to offer as collateral, cashflow from a large dry-cleaning business, and 40% cash, so it only took 5-6 weeks.
If the president wanted to help the economy, he'd make mandatory computer proficiency classes and tests, with refusal and failure punishable by death.
I do not understand how these people I support have managed to operate businesses that sustain people's salaries without knowing the difference between closing and minimizing a window.
Someone's mortgage is going to be paid by a business operating with a person as CEO that cannot get the hang of a right mouse click.
And that CEO is in his 40s. And went to college at a state university.
You'd be shocked at the number of young social workers we see who can't figure out the old Gnome interface on Ubuntu. People that are in their TWENTIES.
@Basil I had a very uptight padawan once upon a time. All the implicit homo-phobo-jokes around the man command used to make him absolutely crazy. I'm usually far too chill to go there, but it was tough to resist murmuring the man query I was running to set him off.
@voretaq7 He left. He's actually trying to get me in at the state hospital, which I may consider going to. They're using some pretty sweet network equipment up there, but it also means my scripting and regular sysadmin skills would likely atrophy as well. Not too sure about that.
@voretaq7 I don't think he's actually straight. I'm pretty sure he's Bi and in denial about it.
@Basil Or at least growing up in a conservative part of the forest here. He'll actually be a pretty awesome guy to hang out with in a few years. Very artsy, but very young still.
I am trying to open a port which is not in use according to netstat.
When I configure IIS to run a Web site on the port, I get the following error:
--------------------------- Internet Information Services (IIS) Manager
--------------------------- The process cannot access the file because...
@EvanCarroll Do I think "Has anyone seen CloudFront run slower than S3?" is a good question? -- No. It's a yes/no polling question. For it to be a good question for Server Fault it would have to include lots more detail
So how the hell does the reopen queue work? One would think that with a Q needing 5 reopen votes, that queue wouldn't go away simply because the question got 5 don't reopen votes.
@voretaq7 And there's the rub. That doesn't make sense to me because not giving a 'do not reopen' is simply a vote for status quo ante that shouldn't increment their state.
Hee. I feel better now. Devs asked me to rescue them from an out-of-sync environment problem they created. Told them that I don't have responsibility for their executation environment and told them the ball is in their court on those servers that they won't allow me to manage.
@Adrian the do not reopen/close? Sort of, but it's better than close/reopen being the only way to get items out of the queue of course. The stats for DNC/etc aren't shown (far as I can tell) to discourage bandwagoning ("Oh, someone said this isn't reopen worth, sure sure")
@BenBrocka Sure. I can see that. But I could also see a hazard of flapping on questions that one groups thinks should be OT for the site and another faction thinks are On-Topic. 5 to close, then 5 to reopen, then 5 to close.
@BenBrocka That said, Dev time is expensive. So it might not be worth building a better system anyway until the problem actually shows up.
So I hear most large companies used fixed storage sizes even when they move to thin provisioning. Does anyone know why? Once you're no longer tied to a specific disk, but rather a pool of disks, what's the benefit of having fixed volume sizes?
the question I asked one of the architects is why we should keep doing it this way, and he gave me the non-answer of "well, I've seen other large shops doing it that way"
@Basil Interesting. I was under the impression that thin provisioning reduced the I/O needs at VM build time but increased I/O load in production because the disk images need to be extended as they grow.
I'm comparing taking 15 14+2 raids and carving a bunch of volumes from them to taking a pool of 15 14+2 raids and carving "virtual" volumes from them, each of which touch all the spindles in all the raids
@Basil I can't think of a reason to force thick provisioning on the SAN. I can see standard allocation sizes for the hosts, but how it gets stuffed onto the SAN doesn't matter - whatever's most efficient.
@voretaq7 We're going thin- that's already been decided. That said, among the list of things we no longer have to do to manage our storage (like name volumes based on their size and never increase the size of a volume), the concept of arbitrary volume sizes is conspicuously (to me) absent
@vCole For production systems, I've been told that even once they migrate to thin technology with pools (not unlike raid-DP aggregates), people tend to stick with their sizing standards, and I don't know why
@Basil Mostly makes very good sense. Wondering how the thin prov. would impact database performance though if the data is spread out in chunks across the platters.
Though I suppose that could be mitigated on busy databases if you're using SSD caching.
I know the nimblestorage stuff keep copies of "interesting" stuff on the SSDs.
@Adrian the concepts of thin provisioning, auto-tiering, and wide striping are all somewhat related. Multiple databases will have statistically better performance if they're all spread across the same pool of disks compared to what they'd get is they were each allocated a fraction of that pool for their own use.
That's wide striping. Thin provisioning is something that you can more safely do when you're working with a large pool because if you overprovision, no single process is likely to generate so many new pages that you'll bust your overallocation limit
@Adrian More spindles means lower seek time, usually
well, the pure seek time per disk is the same, so any IO will have the same average latency, but you will be able to do more IOs with that low latency before you start pushing the latency up higher than if you had less spindles
the way performance normally works is that you have one latency when you're doing a small amount of reads, and another, much higher latency when you're requesting random reads faster than your backend disk can provide them
@Adrian SSD tiering (not on the server, but on the storage) is more generally called auto tiering, and each vendor has their own secret recipe that is better than their competitors'. In essence, the chunks of your data that are highly utilized will drift toward higher performance disk, and the chunks that are low utilization will drift toward the low performance disk, however the volume address and name don't change.
EMC and Netapp have something in place that uses SSD both as the highest tier for permanent storage, as well as sort of a layer two cache, which will promote a chunk from, for example, 7200 RPM nearline disk straight to SSD as soon as it's accessed once, thereby preventing something like a quarterly report from going more slowly than it would have before you turned on auto-tiering
@Basil Ok. And since that's secret sauce stuff, I wouldn't have to worry about that. I definitely remember 5 years ago having to attend meetings with our customer where consultants were wrangling with internal storage staff about tier assignments and spindle allocation.
My primary customer had an awful lot of people who literally had no marketable skills other than managing Oracle tablespaces. Explaining information from our upstream OEM vendor was a royal PITA.
latency is measured from the time it enters the queue till the time it's accepted by the OS. Extraordinarily long queue lengths combined with saturated disk is a recipe for abysmal latency
@Basil this was a graph i plotted with the official netapp formula for calculating latencies. their formula was a little wrong though. It ain't that bad.
I should charge Netapp for correcting their formula
Jesus, that is if you don't have a DNS suffix added.
Eg for Windows PC you can check by:
ipconfig /all
Host Name . . . . . . . . . . . . : PCNAME
Primary Dns Suffix . . . . . . . : local
FQDN = Hostname + Primary DNS Suffix
So in this case: PCNAME.local
@AlexanderJanssen Ah. I was lucky enough to be given a new n3240 to test with a PAM card, and I thought there was something wrong with my load generator, because I couldn't get over 1.5ms latency on random reads
turns out, it was that the entirety of my test data was loaded into the PAM card
@Basil well, i do media-caching with it - and just by transparently telling my proxy to vomit of all those youtube-videos to the FAS made my testcase a tad more valid.
i had more problem with utilizing the port-channel correctly. their loadbalancing algorithm to ports/ips is TOTALLY bizarre!
a netapp engineer gave me the source code to a program which calculates which of the lines from the portchannel will be utilized if a certain source ip and port will be used
man, i deploy my netapps at POPs, we're churning out 20 git/s and transparently serve cached youtube vids - about 50 proxy nodes and all retrieve videos from the netapp. certainly i'm interested in utilizing the portchannel correctly...
@HopelessN00b can I trade in my X.25 for your T1? Although my customer offers 20 gbit for the subscribers, they still use a wee old 64 kbit for remote maintenance on some sites.
@AlexanderJanssen it's rare, but yes. Most of our switches are at least 10/100 now, and we have GB backup networks at more than three quarters of our yards
Today I was testing WAP1-transport again... It reminded me how good mobile networks are working nowadays. As long as someone doesn't try to send an MMS.
even though no one uses WAP anymore, MMS is still transported via WAP
MMS is da ev1l
when my colleague was trying to retriece an MMS from the MMS-Center today with that 1996 Sharp mobile handset, he got this errormessage in German: lh3.googleusercontent.com/-8nRukg1335Q/UH6eqrAqH2I/AAAAAAAABHY/… - It basically say, literally translated: "win you fail again"
(means: the handset wasn't able to retrieve the content from the MMSC - turned out, the URL being sent from the PushProxyGateway was crap, also the secondary PDP context was not configured correctly on the handset9
@MDMarra Had to move the database from one remote SQL server to another, followed the McAfee KB, tested the connection, and upon rebooting the ePO server, getting a database error that prevents me from logging in... which prevents me from say, checking the database configs trhough the web interface.