Are you going to PDC? We are...

dpblogs — Fri, 03 Oct 2008 19:35:00 GMT

Come meet the Velocity Team in the pavilion and learn about Project "Velocity" in our 2 breakout sessions.

Project "Velocity": A First Look presented by Murali Krishnaprasad, Architect

It is predicted that all large applications will use a distributed data cache as the initial tier for all data access. This session presents an overview of "Velocity," Microsoft's distributed in-memory cache, and shows how it works with IIS, ASP.NET, ADO.NET and SQL Server Data Services.

Under the Hood: Velocity Architecture and Future Roadmap presented by Anil Nori, Distinguished Engineer

Velocity is an explicit, in-memory distributed cache. In this talk, we present Velocity's architecture to meet the high performance, scale, and availability requirements of web and enterprise applications. We will discuss mechanisms for data placement, data distribution, and data replication for performance, scale, availability respectively. We will describe mechanisms for providing database capabilities like LINQ support, indexing, concurrency control, and data consistency. We will also present the feature roadmap for Velocity.

More Information about PDC 2008 - Los Angeles, CA - Oct. 27-30
Microsoft's premier developer event, the Professional Developer Conference, is just over 3 weeks away. PDC 2008 will feature more than 160 sessions covering a wide range of topics for professional developers and architects. Each session is delivered by Microsoft engineers, so attendees can expect to receive a high-quality in-depth technical understanding of Microsoft’s future platform along with practical guidance for helping plan the evolution of products and technologies. Microsoft's Chief Software Architect, Ray Ozzie, is set to kick off the event with the keynote. With all the excitement around Visual Studio 2008 and Windows Server 2008, and with SQL Server 2008 just released, this PDC should prove to be a very exciting event. Don't miss it! Here's the link to register.

Creating Multiple Velocity Instances on a Single Machine

velocityteam — Tue, 10 Jun 2008 12:50:00 GMT

This article will guide you through the process of creating more than one instance of Microsoft project code named "Velocity" (henceforth referred to as "Velocity" for the remainder of the article) on one standalone machine. All such instances created on this machine can form a cluster (or multiple clusters), just like it were installed on different machines.

Currently "Velocity" runs as a 32 bit process (even on 64 bit OS) with address space limited to 2GB. So, by creating multiple instances of "Velocity" you will be able to leverage the capabilities of a machine with lot of memory and CPU power.

By default "Velocity" will be installed in "%Program Files%\Microsoft Distributed Cache". This directory contains

"Velocity" DLL’s / EXE’s
Configuration file DistributedCache.exe.config
Other supporting files

The “default” installer that we ship can only install one instance of "Velocity" on a given node. In order to install multiple instances, follow these steps.

[Each "Velocity" instance is referred to as a cache host which is actually a windows service. We will create multiple "Velocity" windows services and add them to the "Velocity" cluster.]

Make sure that you have "Velocity" installed on the machine where you want to run multiple services. Stop the cluster (if it is already running) from the Administration Console (e.g., MyCluster> stop cluster)
Create directories for each of the hosts to be set up in this machine. E.g., If you want to create two more instances other than the one installed, then create directories like "Microsoft Distributed Cache Instance-2" and "Microsoft Distributed Cache Instance-3". Copy all the contents from the installation directory (default: %Program Files%\Microsoft Distributed Cache\V1.0) to these directories.
Create a new Windows service for each of the instances using following command
sc create <serviceName> binPath= "<newCacheHostDir>\DistributedCache.exe" DisplayName= "<displayName>"
Where,
- serviceName – Name of the service to run the new instance.
- displayName – Service name displayed on the services tab.
- newCacheHostDir - Full path of the directory for new cache host.
C:\>sc create DCacheHost2 binPath= "C:\Cluster\Microsoft Distributed Cache Instance-2\DistributedCache.exe" displayName= "My Cache Host 2"

C:\>sc create DCacheHost2 binPath= "C:\Cluster\Microsoft Distributed Cache Instance-2\DistributedCache.exe" displayName= "My Cache Host 2"
Each newly created Windows service will represent a cache host in the "Velocity" cluster. Modify the 'DistributedCache.exe.config' file in respective directories using notepad as follows
1. Modify the cacheHostName to match the “serviceName” specified during the “sc” command above.
2. Set desired log location for new cache host.
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<configSections>
        <section name="dcacheConfig" type="System.Data.Caching.LocalConfigReaderWriter, CacheBaseLibrary, Culture=neutral, PublicKeyToken=null" allowLocation="true" allowDefinition="Everywhere" />
    </configSections>

    <dcacheConfig clusterName="MyCluster" hostName="IMDBSTRS01" cacheHostName="DCacheHost2">
         <config location="C:\ConfigStore\MyCluster" />
        <log location="C:\Cluster\Microsoft Distributed Cache Instance-2\logs" />
    </dcacheConfig>

</configuration>
Modify the clusterconfig.xml file to configure the cluster for these newly created cache hosts. The clusterconfig.xml fill can be found on the network share you specified during installation

Update the 'ClusterConfig.xml' by adding entries for the new cache hosts in the hosts section. You can copy the existing entry and modify following parameters
- hostName – Modify the hostname to match the “hostName” in the DistributedCache.exe.config
- cacheHostName – Modify the cacheHostName to match the “serviceName” specified during the “sc” command above.
- clusterPort and cachePort – These ports should not conflict with other ports on the network (or other cache hosts)
- hostId – Unique identifier for the cache host in the cluster.
- You can choose to edit some of the other parameters for experimenting with "Velocity".
E.g., if you create a cache service with name "DCacheHost2" and "DCacheHost3", example entries would be like:

<hosts>
    <host name="IMDBSTRS01" hostId="1552752876" quorumHost="True"
          cacheHostName="DistributedCacheService" cachePort="22233"
          clusterPort="22234" size="2048"
          lowWaterMark="70" highWaterMark="90" />
   <host name="IMDBSTRS01" hostId="1552752877" quorumHost="False"
         cacheHostName="DCacheHost2" cachePort="22333"
         clusterPort="22334" size="2048"
         lowWaterMark="70" highWaterMark="90" />
   <host name="IMDBSTRS01" hostId="1552752878" quorumHost="False"
         cacheHostName="DCacheHost3" cachePort="22433"
         clusterPort="22434" size="2048"
         lowWaterMark="70" highWaterMark="90" />
</hosts>
Now all the services should be available as part of the windows services.
You can start the services using start cluster command from "Velocity" Administration Tool.

Your 3 node cluster is now up and running! Happy Testing!!!

Sudhir Jorwekar, Arun K S
(Microsoft project code named "Velocity" Team)

Microsoft project code named "Velocity" : Microsoft project code named “Velocity”

Are you going to PDC? We are...

Creating Multiple Velocity Instances on a Single Machine