Any experiences with scaling out with BOS

Some links on the matter (increasing connection limit of 2 on the client side):
Last comment by TWiStErRob:
http://social.msdn.microsoft.com/forums/en-US/netfxnetcom/thread/1f863f20-09f9-49a5-8eee-17a89b591007
Topic opening post:
http://stackoverflow.com/questions/866350/how-can-i-programmatically-remove-the-2-connection-limit-in-webclient
Some people are complaining about the fact that 2 is some kind of RFC standard (for HTTP 1.1?), but honestly I don't care.

The .ibconfig information is for DevForce only, and is not used by the Remoting system. Generally, if you don't include a .config file with the system.runtime.remoting section, DevForce will configure remoting using information in the .ibconfig, along with both DevForce and Remoting defaults.

Here, since you need to modify a configuration setting which is not supported within the .ibconfig file, you'll need to specify the system.runtime.remoting information entirely so that the Remoting system can auto-configure from the .config file.

I'm not sure what other settings you might have in your web.config file (eg, for authentication), but based on the .ibconfig information you show and the .config file I sent previously, the only change needed to the info in the .config is to set the correct URL:

url="http://10.10.131.118/BOS/PersistenceServer.rem"

You'll still need your .ibconfig file too, as DevForce will still use that. So, on the client side, you'll have both the .ibconfig and .config files, or you can consolidate into a .config file containing both DevForce and Remoting information.

Also make sure that the references to the DevForce assemblies are set as "copy local" so that the assemblies will be copied to your application bin folder.

To anybody who reads this thread: this (clientConnectionLimit) is about legacy RPC communication and not for WCF.(The stateless behavior of BOS is true for every setup though).

Edited by ctoth - 18-Mar-2013 at 1:34pm

Regarding the issue with only 2 connections from a client at one time - this is the default setting for a client remoting channel. To change it you can set the clientConnectionLimit in a client-side app.config file.  I've attached a sample.uploads/11/App.zip

I was experimenting a little with BOSes. We use remoting/RPC instead of WCF to connect to the BOS. In order to rule out the effect of database blocking to the results I just introduced dummy work to be done on the server (Thread.Sleep). The following finding is true for a single BOS setup: I went up to 10 connected clients. Their work tasks executed parallelly on the server, but not more than 2 at a time from a given client. So if all the 8 clients issued 10 work tasks request of 20 seconds of work at the same time, than a pair of work items executed at once only at a time. So 20 work items were done after 20 seconds, the next 20 (a pair of tasks from each client) the next 20 seconds and so on.
This is even true if I connect with a single client to the BOS and issue 15 tasks. Only a pair is executed at once.

Question: what kind of parameter or setting causes that? Is there a configuration or properties switch which tunes thread pool size or connection pool size for the BOS? ASP.NET has a 25 thread/CPU default limit, but maybe that's only for the web server core listener which spawns the actual worker threads later? Is there some configuration for the BOS itself?

Thanks,
Csaba

The exact version is "3.7.5.0".

You are right. I wanted to say DevForce Classic. I guess I opened this topic in the wrong forum.


Edited by ctoth - 06-Mar-2013 at 11:26am

Thanks for the heads up sbelini.
I realized that I forgot to mention a very important fact: we use the Classic version of DevForce 2010, not the version for EntityFramework. I think your statements (except notification) are true for the classic also. I need to look at how refetch goes with Classic.
I'm new to IdeaBlade BTW.