Cluster wikiload project - Revision history

Heth at 14:59, 2 April 2009

2009-04-02T14:59:31Z

2009-03-30T06:14:39Z

‎Limitations

2009-03-16T06:55:23Z

‎LMS

2009-03-16T06:53:43Z

2009-03-16T06:53:27Z

‎Implementation

2009-03-15T19:12:36Z

‎Skeleton

2009-03-15T13:29:11Z

‎Implementation

2009-03-15T13:25:52Z

‎LC - Lobster clients

2009-03-15T13:25:46Z

‎Skeleton

2009-03-15T13:23:59Z

‎Project faces

@@ Line 1: / Line 1: @@
 =Purpose=
 The purpose of this project is to build a distributed program which run on several workstations loading a Wiki server farm. The aggregated load from all workstations can stress the serverfarm and gather information to get idea of how the serverfarm performs.
@@ Line 45: / Line 44: @@
 *State 21: Send keepalive every 5 second to ''monitor session'' if three sent without ''acknowledge'' send ''die'' and then die.
 ** Load server and report in keepalive packets load.

@@ Line 4: / Line 4: @@
 == Limitations ==
 This is not a program to measure the performance. The time needed to build such a system exceeds the time at hand.<br/>
-Another limitation is that its targeted to [www.mediawiki.org MediaWiki] and not as a general workload framework. Though I will try and separate the skeleton from the MediaWiki stuff, to make it easier to implement in other environments.
+Another limitation is that its targeted to [http://www.mediawiki.org MediaWiki] and not as a general workload framework. Though I will try and separate the skeleton from the MediaWiki stuff, to make it easier to implement in other environments.
 == Name ==
 [[Image:Lobster.gif|right|200px|thumb]]

@@ Line 16: / Line 16: @@
 * Moose For object orientated. - Perhaps
 * IO::Socket::Multicast for the LMS auto discovering the LC's. (No time, needs stuff compiled in on Windows)
-* [[POE - portable multitasking and networking framework for Perl | POE::Compont::Server::TCP]] as multitasking TCP server
+* [[Perl_POE| POE::Compont::Server::TCP]] as multitasking TCP server
 * TK for making a GUI on the LMS. (Takes a long time. Perhaps I will just use Curses also here)
 * Storable for saving results to disk. (A bad idea but very fast to implement.)
 ==LC's==
 * Moose For object orientated. - Perhaps

@@ Line 16: / Line 16: @@
 * Moose For object orientated. - Perhaps
 * IO::Socket::Multicast for the LMS auto discovering the LC's. (No time, needs stuff compiled in on Windows)
-* [[POE - portable multitasking and networking framework for Perl POE::Compont::Server::TCP]] as multitasking TCP server
+* [[POE - portable multitasking and networking framework for Perl | POE::Compont::Server::TCP]] as multitasking TCP server
 * TK for making a GUI on the LMS. (Takes a long time. Perhaps I will just use Curses also here)
 * Storable for saving results to disk. (A bad idea but very fast to implement.)

@@ Line 13: / Line 13: @@
 == Implementation ==
 Because of the tight time schedule I've decided to implement it using Perl and the following modules.
-* Moose For object orientated.
+== LMS ==
 * WWW::Mechanize as the HTML Client engine.
 * POE::Session as the multitasking engine on the LC's to load the serverfarm
 * Curses for controling the Screens of the LC's (Perhaps also for the LMS)
 = Project Schedule=

@@ Line 32: / Line 32: @@
 ** Keepalive packets every 10 seconds else go to state 1
 *State 3: Fetch one page (Several attemps with 10 Seconds timeout) from serverfarm if OK go to state 10 else go to state 4
-*State 4: Report Error to Connect error to LMS
+*State 4: Report Error to Connect to LMS go to state 3
 *State 10: Start monitor session go to state 11
 ** monitor session get results from Workload session and report every 10 sec. to LMS
-*State 11: Start Workload sessions reporting to monitor session.
+*State 11: Start each Workload sessions in state 20.

← Older revision		Revision as of 13:25, 15 March 2009
Line 27:		Line 27:
	== LC - Lobster clients ==		== LC - Lobster clients ==
	=== Skeleton ===		=== Skeleton ===
		+	*State 1: Connect to the LMS then go to state 2
		+	*State 2: Wait for orders from LMS then go to state 3
		+	** Keepalive packets every 10 seconds else go to state 1
		+	*State 3: Fetch one page (Several attemps with 10 Seconds timeout) from serverfarm if OK go to state 10 else go to state 4
		+	*State 4: Report Error to Connect error to LMS
		+	*State 10: Start monitor session go to state 11
		+	** monitor session get results from Workload session and report every 10 sec. to LMS
		+	*State 11: Start Workload sessions reporting to monitor session.

@@ Line 24: / Line 24: @@
 === Skeleton ===
 Built as a statemachine
 == LC - Lobster clients ==
 === Skeleton ===