I'm writing this more to clear my head than anything else. If it helps someone, great. We have measured significant 'release impact' when deploying one of our core applications. The main problem is initialization/warmup of the appPool. We've tried the built-in methods, but for whatever reason we are always stuck with ~25s of dead time while the first request warms things up (we assume it's warming things up, not really sure what is happening). After that 25s wait things are very snappy and fast, so how do we prevent all of our web servers from going into 25s of dead time with production traffic inbound? Starting point - why do this? We care about our customers, and we want to help drive our business forward with as much quality/safety/speed as possible. Because we want to drive our business forward, we are pushing to do more and more deploys ( currently we do a daily deploy, but want to see 5x that ) ( if you have to ask why we want 5x, read this ).
tl;dr Built a custom keyboard cuz I have weirdo nerve pain issues. Learned a lot cuz I failed a lot. Maybe 'do it right the first time' is a bad frame of mind. The keyboard ended up being kinda nifty. It has lights, and a trackball, and QMK, and it helps my issues. \o/ ( tl;dr is internet lingo that means, too long; didn't read ) Pain as a key ingredient An old proverb says, 'necessity is the mother of invention', and that is how this story begins. Over the last few years, age or stress or something has caught up with me and I developed the need to change my human-to-computer interface. Mousing changed to trackballing. The traditional keyboard was swapped out for an ergonomic, and then split keyboard. Complicated multi-finger-and-hand key combinations were replaced by single keypress macros. And yet more was still needed. It's often said that change only happens with pain - indeed, the organizations many of us work in seem to apply this as law - an
This warning isn't documented that well on the googles, so here's some google fodder: You are trying to set up replication for a DFS folder (no existing replication) Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2) You have no issues getting replication configured You see the DFSR folders get created on the other end, but nothing stages Finally you get EventID 4312: The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved. Additional Information: Folder: F:\Users$\user.name\Desktop\Random Folder Name\ Replicated Folder Root: F:\Users$ File ID: {00000000-0000-0000-0000-000000000000}-v0 Replicated Folder Name: Users Replicated Folder ID: 33F0449D-5E67-4DA1-99A
Comments
Post a Comment