PCampBot - Revision history

Manni at 11:42, 4 December 2023

2023-12-04T11:42:53Z

Ferd Frederix: /* Step 1: Create bot accounts */

2023-03-11T23:31:31Z

‎Step 1: Create bot accounts

Ferd Frederix: underscore is no longer used in bot names.

2023-03-11T23:30:55Z

underscore is no longer used in bot names.

Acryline: /* Step 5: Disconnect bots */

2021-09-24T10:37:55Z

‎Step 5: Disconnect bots

Acryline: /* Example */

2021-09-24T10:37:00Z

‎Example

Manni: /* Step 2: Start pCampbot */

2016-10-10T12:06:24Z

‎Step 2: Start pCampbot

Justincc: Inbound and outbound resends are now recorded

2014-08-01T18:21:10Z

Inbound and outbound resends are now recorded

Justincc: /* Step 4: Assess performance */

2014-01-13T21:47:55Z

‎Step 4: Assess performance

Justincc: /* Step 4: Assess performance */

2014-01-13T20:32:06Z

‎Step 4: Assess performance

Justincc: /* Caveats */

2013-11-01T01:56:45Z

‎Caveats

← Older revision		Revision as of 11:42, 4 December 2023
Line 1:		Line 1:
−	{{Quicklinks}}	+	{{Quicklinks\|PCampBot}}

	= Using pCampbot as of OpenSimulator 0.7.6 =		= Using pCampbot as of OpenSimulator 0.7.6 =

@@ Line 53: / Line 53: @@
 === Step 1: Create bot accounts ===
-The first step is to create 5 bot accounts, all with the same password.  Each bot account must have the same first name and the same last name prefix.  But each bot must also have its last name prefix appended with an underscore (_) and its bot number, starting from 0.  In this case, we want five bots, and lets suppose we will call them "ima bot".  Then the five accounts that we want are
+The first step is to create 5 bot accounts, all with the same password.  Each bot account must have the same first name and the same last name prefix.  But each bot must also have its last name prefix appended its bot number, starting from 0.  In this case, we want five bots, and lets suppose we will call them "ima bot".  Then the five accounts that we want are
   ima bot0

@@ Line 11: / Line 11: @@
    -s, -start         start location for bots (optional).  Can be "last", "home" or a specific location with or without co-ords (e.g. "region1" or "region2/50/30/90"
    -firstname         first name for the bots (required)
-   -lastname          lastname for the bots (required).  Each lastname will have _<bot-number> appended, e.g. Ima Bot_0
+   -lastname          lastname for the bots (required).  Each lastname will have <bot-number> appended, e.g. Ima Bot0
    -password          password for the bots (required)
    -n, -botcount      number of bots to start (default: 1) (optional)
-   -f, -from          starting number for login bot names, e.g. 25 will login Ima Bot_25, Ima Bot_26, etc.  (default: 0) (optional)
+   -f, -from          starting number for login bot names, e.g. 25 will login Ima Bot25, Ima Bot26, etc.  (default: 0) (optional)
    -c, -connect       connect all bots at startup (optional)
-   -b, behaviours     behaviours for bots.  Comma separated, e.g. p,g.  Default is p (required)
+   -b, behaviours     behaviours for bots.  Comma separated, e.g. n,p,g.  Default is p (required)
      current options are:
         p (physics  - bots constantly move and jump around)
@@ Line 55: / Line 55: @@
 The first step is to create 5 bot accounts, all with the same password.  Each bot account must have the same first name and the same last name prefix.  But each bot must also have its last name prefix appended with an underscore (_) and its bot number, starting from 0.  In this case, we want five bots, and lets suppose we will call them "ima bot".  Then the five accounts that we want are
-  ima bot_0
+  ima bot0
-  ima bot_1
+  ima bot1
-  ima bot_2
+  ima bot2
-  ima bot_3
+  ima bot3
-  ima bot_4
+  ima bot4
 The classic way to create a user account is to do it by using the "create user" command on the OpenSimulator standalone or Robust service console, depending on whether one is running in standalone or grid mode.  However, this can be laborious, particularly if one needs hundreds of bot accounts.  There's a very basic python script at https://github.com/justincc/opensimulator-tools/blob/master/create-user-line-generator/src/culg.py ( dead link ) which will generate the user lines needed, giving each account a non-random UUID for later debugging purposes.  The lines that this script generated can be pasted directly into the OpenSimulator console.

← Older revision		Revision as of 10:37, 24 September 2021
Line 102:		Line 102:

	at any time.		at any time.
		+
		+	[[Category:Testing]]

@@ Line 61: / Line 61: @@
   ima bot_4
-The classic way to create a user account is to do it by using the "create user" command on the OpenSimulator standalone or Robust service console, depending on whether one is running in standalone or grid mode.  However, this can be laborious, particularly if one needs hundreds of bot accounts.  There's a very basic python script at https://github.com/justincc/opensimulator-tools/blob/master/create-user-line-generator/src/culg.py which will generate the user lines needed, giving each account a non-random UUID for later debugging purposes.  The lines that this script generated can be pasted directly into the OpenSimulator console.
+The classic way to create a user account is to do it by using the "create user" command on the OpenSimulator standalone or Robust service console, depending on whether one is running in standalone or grid mode.  However, this can be laborious, particularly if one needs hundreds of bot accounts.  There's a very basic python script at https://github.com/justincc/opensimulator-tools/blob/master/create-user-line-generator/src/culg.py ( dead link ) which will generate the user lines needed, giving each account a non-random UUID for later debugging purposes.  The lines that this script generated can be pasted directly into the OpenSimulator console.
 === Step 2: Start pCampbot ===
-The next step is to start up pCampbot with the required connection parameters.  Let us suppose that you want to test against a region called "r1" on a local grid with a loginuri of http://192.168.1.2:8002.  Let us assume that you've given the bots the password "plentyofruth". The command to run is then
+The next step is to start up pCampbot with the required connection parameters.  Let us suppose that you want to test against a region called "r1" on a local grid with a loginuri of <nowiki>http://192.168.1.2:8002</nowiki>.  Let us assume that you've given the bots the password "plentyofruth". The command to run is then
-  mono --debug pCampBot.exe -loginuri http://192.168.1.2:8002 -s r1 -firstname ima -lastname bot -password plentyofruth
+  mono --debug pCampBot.exe -loginuri <nowiki>http://192.168.1.2:8002</nowiki> -s r1 -firstname ima -lastname bot -password plentyofruth
 This will start up pCampbot and you'll see a familiar console command line as you would on a simulator or Robust console.  As with the other consoles, you can type "help" to get a list of commands.

@@ Line 86: / Line 86: @@
 However, one needs to be extremely careful if logging in using a viewer on the same machine from which the bots are running.  The bots should really be running from a different machine or ideally even from a different network in order to get a more accurate picture of current simulator performance.
-One can also look at [[Monitoring|server side monitoring]], particularly "show stats clientstack" which will show various client stack related statistics (this is the part of the OpenSimulator code that handles receiving and sending of UDP messages from viewers).  In particular, the InboxPacketsCount should be constantly 0 or near 0 - a build up here means that your simulator is receiving UDP packets quicker than it can process them.  Unfortunately, these server-side statistics are still evolving and important measures (such as number of inbound and outbound resends) are still not recorded as of OpenSimulator 0.7.6.
+One can also look at [[Monitoring|server side monitoring]], particularly "show stats clientstack" which will show various client stack related statistics (this is the part of the OpenSimulator code that handles receiving and sending of UDP messages from viewers).  In particular, the InboxPacketsCount should be constantly 0 or near 0 - a build up here means that your simulator is receiving UDP packets quicker than it can process them.
 === Step 5: Disconnect bots ===

@@ Line 82: / Line 82: @@
 === Step 4: Assess performance ===
-Now this is quite tricky, since there's currently no automated way of assessing simulator or connection performance.  Manual ways to assess this include logging in a viewer to the same region to get a feel for avatar movement (e.g. is it jerky, is there rubberbanding, is chat delayed, etc.) and to see [[Client_side_monitoring|viewer statistics]] such as Ping Sim and Packet Loss.
+Now this is quite tricky, since there's currently no automated way of assessing simulator or connection performance.  Manual ways to assess this include logging in a viewer to the same region to get a feel for avatar movement (e.g. is it jerky, is there rubberbanding, is chat delayed, etc.) and to see [[Client_side_monitoring|viewer statistics]] such as Ping Sim, Packet Loss, Physics Time (frame) and Spare Time (frame).
 However, one needs to be extremely careful if logging in using a viewer on the same machine from which the bots are running.  The bots should really be running from a different machine or ideally even from a different network in order to get a more accurate picture of current simulator performance.

@@ Line 45: / Line 45: @@
 * A pCampBot synthetic bot load is still an extremely poor proxy for a 'real' connection (i.e. a real human being logging in with a viewer and doing all the things they expect to be able to do in a virtual world).  Real connections are very likely to place different stresses on the simulator so real-world performance may be considerably different and poorer than synthetic load tests would suggest.
-There are some things you can do to improve this in pCampbot.  For instance, if you have RequestObjectTextures set in pCampbot.ini then pCampbot will request textures for all objects it sees.  This is both much less stressful than a real scenario (since for a particular sets of bots textures are only requested once) and more stressful (since there is never any caching).
+* There are some things you can do to improve this in pCampbot.  For instance, if you have RequestObjectTextures set in pCampbot.ini then pCampbot will request textures for all objects it sees.  This is both much less stressful than a real scenario (since for a particular sets of bots textures are only requested once) and more stressful (since there is never any caching).
 * pCampbot does currently not work well if there are any surrounding regions.  Avatars will currently just walk off into oblivion.  You must either build fences or remove such regions.  In testing so far, the presence of neighbouring regions does not have any great impact on performance in the region occupied by bots.  However, these tests were performed with blank surrounding regions - surrounding regions containing objects will place more initial stress on the bot connections as object data is downloaded (and textures if this option is active).