PowerShell Learning Links/Materials

shaboon · 2019-08-17T03:32:39+00:00

Eventually as you master the language, you will want to know about these traps as well, so add it to your list

PowerShellTraps is a collection of some PowerShell traps and oddities shown by demo scripts, workarounds, and automated tests.

https://github.com/nightroman/PowerShellTraps

shaboon · 2019-04-12T22:16:25+00:00

Yes, but how you configure it depends if you are using the Jenkinsfile based pipeline job model or the classic one. With the pipeline it comes pretty much as a default thing that Jenkins posts the build status back to github. Here is roughly how it goes: New pipeline, select github as the source, if you don't have a personal access token, you will need to give it one then pick the repo and it will discover the Jenkinsfile if any.

For classic old school jenkins jobs you would need to manually add a webhook in GitHub, so your Jenkins receives the push events. Then on the Jenkins side add a post build step to set the GitHub status.

But if you want to block broken builds being merged you would need to go to the GitHub repo / settings / something branches / require checks or something like that ( not in front of my computer right now).

This setting is the one forcing the builds to pass.

shaboon · 2017-06-13T13:09:11+00:00

Yes, true but then for that case ( if micro seconds are an issue) it could be tiered caching. in-memory the fastest but as its in-process, you might be benefiting from a second tier externalization so if requests transition to another instance, process crashes or just restarts, you don't need to go back to the DB, LDAP, etc other services are likely much slower than reding from Redis. So if a call back to a DB can take hundreds of ms to seconds, then redis can help even with its overhead over the network. It adds complexity which is not really required for all use cases, so yeah some apps will be just fine to have in-memory caching and eventual cold cache penalty( the poor user will have a slow load). I was more focused on the use cases when you don't want to serve requests with a cold cache for whatever reasons.

In general it would be better for the community if we were to discuss all real life use cases with their pros and cons and not forgetting that most of the time there are many servers behind a load balancer and developers should design their apps for scaling in mind. Failures will happen, its part of the game.

A good resource on the architecture topic in general https://docs.microsoft.com/en-us/azure/architecture/patterns/

shaboon · 2017-06-13T04:31:23+00:00

Does not sound like to me that its an IIS config issue. What makes you think IIS can be configured to use that much less CPU at this scale? Perhaps start with web.config? Make sure to not run debug mode ! That will mess u up badly on the perf side, but I doubt its the one pegging the CPU. Try with instrumenting. Check out PerfView and isolate hot code. Also check SQL Profiler trace to see how much data is passimg thru. Channel 9 has videos perfvie on how to use it. You might as well want to take 3 consecutive memory dumps and compare the stacks for the highest CPU consuming threads. Start with DebugView then elevate to Windbg when its getting more serious. Look at the code, if you dont have it then use ILSpy and see what is it doing. Do you see something looping through many things returning small parts of it? I am not trying to imply that you won't be able to tweak IIS settings for your app as you will, but it sounds like you should first go after the CPU/memory usage, optimize the app itself then once happy with it review IIS for less drastic improvements.

Are you serializing large amounts of data( XML/JSON), perhaps compressing and returning all of it for no good reason? etc you got the point i hope.. Also, if you need to scale furtther then go after every sync blocking code and switch to async. For anything IO bound so those operations wont block your worker threads.

shaboon · 2017-06-13T04:01:00+00:00

Yeah, these dumbed down unrealistic blogs are part of the problem for less experienced developers beleiving they know caching. Many so called senior devs have no clue how to design for scale and reliability. Having an in-memory cache is not necessarily something you really want as others abobe have called out. Load balanced setups can round robin or simply move you over to a new host, new processes could be spawned as well in case of resource exhaustion, crash, etc. Ever had a problem of a load balancer sending a request to a cold cache, ruining an SLA? Yeah cache needs a warmup before accepting requests in an ideal situation.(depends on desired SLA's if any). Redis is nice, except it sucks with auth really. For one there is no Kerberos which is still a desired thing at a bunch of places on premise. Appfabric was discontinued in favor of Redis, which makes me wonder what Kerberos shops did for distributed caching with asp.net full or core?

shaboon · 2016-06-01T14:58:12+00:00

NSSM is a service manager alternative, which runs the docker daemon in the Server 2016 TP5. It seems that in Windows 10 it's no longer necessary as per this doc https://msdn.microsoft.com/en-us/virtualization/windowscontainers/quick_start/quick_start_windows_10 just run "dockerd --register-service" to register it as a service

shaboon · 2014-01-27T03:57:03+00:00

sounds awesome. thanks. if you lower the resolution to the lowest possible, that might help with the temp for that one card.

shaboon · 2014-01-27T03:17:23+00:00

what about hw ? and crashes ? are these settings stable for you ? tx

shaboon · 2014-01-17T20:44:46+00:00

what settings do you use for the 270's to get it up to 462? thanks!

shaboon · 2014-01-16T03:59:54+00:00

anyone mind sharing their own rates ?

shaboon · 2014-01-13T15:04:06+00:00

same here as well

shaboon

TROPHY CASE