Search results

We publish multiple samples in the installation directory (C:\Program Files\ScaleOut_Software\StateServer\samples\DotNet by default); the simplest sample is NC_Sample.cs. Alternatively, if you're simply looking to verify the health of your store, you can issue a "Test Store" command from the...

This is a duplicate question--please see this forum thread.

ScaleOut ASP.NET Session provider uses Microsoft default BinaryFormatter serializer. If you're concerned about serialization cost (performance or size wise) for some of your objects stored in session, the best way to address it would be to implement ISerializable interface for these types so you...

Yes, when launching ScaleOut StateServer and related products on the AWS Marketplace, they all launch into the same availability zone. This is by design for two reasons: Host-to-host latency is increased in multi-AZ deployments, which negatively impacts the distributed membership protocol since...

ScaleOut uses multicast for automatic discovery of hosts on your network, but multicast does not get routed across subnets. (This is considered a feature of multicast--your router won't spam every subnet in your network with every multicast packet.) You can work around this by disabling...

The current version of the NamedCache stores lock state internally in thread-local storage, so it's incompatible with async calls that might continue on a different thread. (It's a lot like why you can't use await inside a C# lock{} statement.) We're redesigning how our internal lock tickets are...

Update: As of November 2018, the new async-capable API mentioned in this thread is available in beta on nuget.org [nuget link]. The new library supports the locking operations discussed here by providing methods such as ReadExclusiveAsync. Original Response: Yes, async/await support is under...

Yes, there is a Java API for accessing a remote ScaleOut StateServer (SOSS) store. To use our Java libraries from a remote client machine, install the SOSS remote client installation on Windows or Linux. Configure the remote client to connect to the remote SOSS store. Once the remote client has...

This is an unusual exception--we've have a number of people using SOSS in conjunction with NHibernate for years (even integrating SOSS as a second-level cache provider), but this hasn't been reported before. Without being able to reproduce this we'll need to look for other people reporting...

Hi Vladimir, No, you didn't miss anything--the internal stored by the service is deliberately lean for the sake of efficiency. As you've already noticed, the object's original TTL is tracked, but that's mainly so that it can be reset back to its original value if you're using sliding timeouts...

This is not an expected behavior. We have ran a similar test and could not reproduce the issue, so we think it might have some environmental factor. Please be specific with the version of SOSS you are running, the number of stores, the number of hosts in each store and the number of hosts that...

The SOSS Console relies on Windows GUI components that are not available on Server Core editions of Windows. The ScaleOut StateServer service will need to be managed using the soss.exe command line utility, which offers the same functionality as the Console. Also, the soss_params.txt file, which...

SOSS version 5 uses additional memory of about 650 bytes per object to support advanced features not available in version 4, such as property-based query and remote store access. Version 5 also expands its use of data partitioning, internal hash tables, and memory buffers to maximize performance...

ScaleOut StateServer is an in-memory data grid, so all objects are held in-memory (stored as binary blobs) for the lifetime of the object to gain the benefits of faster data access times of RAM vs. disk. The backing store adapter (IBackingStore) is intended to read/write data grid contents...

The cookieless session state is a standard feature of the ASP.NET pipeline and it is not related to the type of session provider being used. ScaleOut ASP.NET session provider does not play any role with the way the session state is persisted by browser between user's web requests (whether via...

Typically not, but you'll need to rebuild your app if the project directly references the soss_mgtdotnet assembly that you listed above. (It's actually a little unusual to reference soss_mgtdotnet in a client application--people typically only do this for management utilities). But if your...

ScaleOut StateServer (SOSS) was not designed to be a replacement for traditional relational databases—rather, it is designed to be a high-performance, highly-available, distributed key/value store. As such, it does not support full-blown SQL query semantics, and it does not ship JDBC/ODBC/OLEDB...

Hi Marc, Assuming you're running on Windows, I'd suggest using the service's performance counters to alert you about any changes in the farm's membership. So, in Windows Performance Monitor (or whatever monitoring system you use, like Nagios, etc.), you can create a user-defined Data Collector...

The following techniques and best practices can be used to improve ASP.NET application performance when it uses ScaleOut StateServer (SOSS) as an ASP.NET Session provider: 1. Minimize network usage and serialization overhead by reducing session size. All objects in a user’s session state are...

Yes, you can handle WriteBehind events on remote clients. ScaleOut StateServer (SOSS) provides a scalable event handling architecture to scale the throughput of event handling as the workload increases and servers are added to the store. Each SOSS server signals events to its registered client...