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.

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users. This information might be useful in the future when we need to decide where we want to keep and manage our users. Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

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.51 EF 6.0.2 VS2013 It see

Cloud as a Story - Vunvulea Radu

Search This Blog