Search results

  1. M

    threads blocking on read to scaleout server after moving to .NET 5

    That's a little surprising. Do you have a "hot object" that's accessed much more frequently than any other? (If so, whatever client cache partition it falls into will get hammered and eventually become a bottleneck... so scaling the number of client cache partitions may not help in that case.)...
  2. M

    threads blocking on read to scaleout server after moving to .NET 5

    Hi, thanks for the update. It would appear that the bottleneck moved out of the connection pool and up into the client cache. This might actually be good progress! Try increasing the number of client cache partitions to reduce the contention there. You can do that through the partitionCount...
  3. M

    threads blocking on read to scaleout server after moving to .NET 5

    No, it's the opposite: you want forceManagedLocking to be set to false to get the new, "optimized" locking behavior.
  4. M

    threads blocking on read to scaleout server after moving to .NET 5

    OK, I've posted Scaleout.Client version 4.2.10 on ScaleOut's development NuGet feed. You'll need to add http://nuget.scaleoutsoftware.com/nuget as a package source and then make sure this source is selected in the NuGet package manager. (See Microsoft’s Package Sources topic for details on...
  5. M

    threads blocking on read to scaleout server after moving to .NET 5

    I applied the locking change to our .NET Core build, but it did not improve performance in our tests--we saw that the performance on .NET Core 5/6 was already very good, even slightly better than the optimized .NET Framework behavior under the same load (500 threads vying for resources from a...
  6. M

    threads blocking on read to scaleout server after moving to .NET 5

    Yes, we'll move forward to get that optimization into .NET Core.
  7. M

    threads blocking on read to scaleout server after moving to .NET 5

    I don't think you'll see a difference in performance of the core library functionality if you upgrade to the latest. Most of the changes since 3.1.4 have involved adding support for advanced features in the service (GeoServer, PMI, etc.). There was one important fix in 4.2.7 involving client...
  8. M

    threads blocking on read to scaleout server after moving to .NET 5

    OK, so you're still running with a whole lot of threads. We can research to see if there's a similar optimization available for the .NET Core build. But, if possible, I would try moving to the async Cache methods and at least test to see if there's an improvement. I'm almost certain it'll help...
  9. M

    threads blocking on read to scaleout server after moving to .NET 5

    A few questions: How many threads do you see blocked on GatewayMultiplexer.GetGatewayFor()? Hundreds? What operating system are you running on? Is it possible for you to move to async calls and keep your app's thread count down? For background, I looked through old support cases and pieced...
  10. M

    NullReferenceException at Scaleout.Collections.RecentDictionary

    Hi Nadav, just a one-week check-in: have you had an opportunity to deploy 1.0.4 and determine whether it helped?
  11. M

    NullReferenceException at Scaleout.Collections.RecentDictionary

    Thank you. The line number appears related to the fix we made, so I think there's a very good chance it's resolved. I cannot say it's fixed with 100% certainty because we still aren't able to repro this particular exception--the error here is a result of corruption that occurred in the cache at...
  12. M

    NullReferenceException at Scaleout.Collections.RecentDictionary

    Hello again Nadav, We found and resolved an issue in the Scaleout.Collections NuGet package that may explain the exception that you reported. Please update your project to use version 1.0.4--we'll be interested to hear if this resolves the issue. Thanks!
  13. M

    NullReferenceException at Scaleout.Collections.RecentDictionary

    Hi Nadav, We've reviewed error you reported and haven't yet located the source of the problem. Please copy the Scaleout.Collections.pdb file from the attached zip to the web server(s) that are experiencing this issue--it should be copied to the same folder as the Scaleout.Collections.dll file...
  14. M

    NullReferenceException at Scaleout.Collections.RecentDictionary

    Hi Nadav, Thank you for reporting this and supplying the stack trace. We'll investigate and will let you know what we find.
  15. M

    Usage of SOSS with Nuget

    Update: We're changing the server to return an error to the client instead tripping a consistency check and restarting. The exception thrown back to the Cache caller will help track down which type is causing the problem.
  16. M

    Error - Cannot access a disposed object

    Thank you for those answers. I do not yet see a usage pattern or a mistake that you could make that would explain this -- the ObjectDisposedException is complaining about long-lived thread-local resource that the ScaleOut library never disposes. We need to learn more about your environment...
  17. M

    Error - Cannot access a disposed object

    Hi YardenK. This is not a known issue. Is the exception thrown when your app first starts up or does is only occur after your app has been running for a long time? What kind of threading model does your app use? Is this just a regular ASP.NET app serving web requests, or does your app start a...
  18. M

    Usage of SOSS with Nuget

    The two libraries ignore each other's [SossIndex] attributes, so using both should be fine. However, for every indexed property, I would check to make sure that the same HashIndexPriority value is passed into the constructor of both versions of the attribute. But it's interesting that you left...
  19. M

    Usage of SOSS with Nuget

    Did your app’s usage of the [SossIndex] attribute change when you migrated to the Scaleout.Client nuget package? The log indicates that the server encountered an error as an object was being added to the cache--the service was indexing properties marked with the [SossIndex] attribute and found...
  20. M

    ScaleOut Management Console is blank

    Are you experiencing this with the latest release of ScaleOut? Version 5.10.4.359 of the ScaleOut Product Suite addressed this empty screen issue. Otherwise, Oleg's fix (starting the soss_console.exe application with the -RESET flag) will work if you're running version 5.7 or later. If you're...
Top