Skip to main content

New Windows Azure instances full with steroids

This days Microsoft launched two new types of instances – A8 and A9. This two new type of instances are like a bulldozer from the perspective of the available RAM memory and processor. Each of this machines has 8 and 16 virtual cores and 56GB and 112GB of RAM memory. Yes, you heard me good 112GB on RAM memory available on cloud instances.
For customers, that has intensive work to do this is a great news. Starting from now it will be pretty easy to have an intensive processor tasks that are processed on the cloud, without having to use multiple machines. Another opportunity is for the applications that needs to use a lot of memory – cache systems for example. For this kind of system, having more than 100GB of memory available is great. If we think a little bit, we can imagine a scenario where we have 100GB of data loaded from a relational database into a cache. This is great!
But, this is not all. This new kind of instances are more than an instance of steroids. This are a new generation of instances, that has not only more CPU and RAM but also other new features (see below).
Having an instance on steroids can be without real value if you don’t provide the perfect environment where to use all this power. Because of this, A8 and A9 instances have Remote Direct Memory Access (RDMA) and InfiniBand.
RDMA is a features that allows two different computer to access directly the same memory without using the operation system infrastructure. Basically, in this way we have a low-latency network with an extremity high-throughput. This is a part of the key to have an instance that can be used for massively parallel processing.
This mechanism allow us to transfer data from application with zero-copy time (we don’t need to copy the content between application or use buffers). The advantage of this feature is almost 0 resources required from CPU, cache or context switches. Theoretically, using this feature we can move 4GB of data that is in memory between two machines in under 1 second.
The second feature, which unlocked RDMA and also allowed high throughput is InfiniBand. This allow a fast connection between processor nodes and I/O nodes. In this way all the resources can be used at maximum level. If you hear about InfinitiBand for the first time, you should know that this is not a traditional Ethernet network architecture. It is based on a switched fabric topology. All the information that is transmitted is in form of packages that form a message. Each message can have different types like:

  • Atomic Operation
  • Multicast Transmission
  • Channel Send or Receive
  • Transaction Based Operation
  • Direct Memory Access (RDMA)

This two feature enabled Messaging Passing Interface (MPI). This system is to sustain application that needs to be large scalable application. You should know that MPI is not specific to Microsoft stack (you can use different languages to write application for it Fortran).
This new types of instances can be used with success for application from different domain likes: weather modeling, science, different simulation or intensive computing tasks that can be parallelized.

Comments

Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…