Aeolus: Performance

From Pmgwiki

Revision as of 00:01, 23 February 2011 (view source) Dcurtis (Talk | contribs) (→Data to be collected for SOSP paper) ← Older edit		Revision as of 00:03, 23 February 2011 (view source) Dcurtis (Talk | contribs) (→Data to be collected for SOSP paper) Newer edit →
Line 23:		Line 23:
	## (ok) Shared Locks: Lock, unlock		## (ok) Shared Locks: Lock, unlock
	# Monster.com: non-aeolus vs. aeolus		# Monster.com: non-aeolus vs. aeolus
		+	## complete setup code: adding companies to workers
		+	## see if one queue for results works
		+	## time basic resume matching
		+	## review infoflow control usage
	----		----

---

Revision as of 00:03, 23 February 2011

Data to be collected for SOSP paper

1. Preliminaries
   1. Configuration
      1. Will be competing with James for machines for SOSP
      2. Eigenharp, Badger, Qubit, Theremin are the fastest machines. The farm is best when lots of machines needed
      3. Is the Authority Service on the same machine that runs the benchmarks?
         1. ok for micro benchmarks (because different processor cores will be used, but big monster should really be distributed
         2. also test to see if it makes a difference
      4. Turn off logging and turn off the file service (No interest in fs benchmarks)
   2. (ok) indicates that the current benchmark code is somewhat reasonable
   3. (P) indicates that the benchmark is mentioned in the current paper
   4. List based on Winnie's thesis; Vicky's thesis computes "with and w/out logging"
2. Forks and calls
   1. (ok) aeolus fork, call with a different pid, same pid, public pid; native call
   2. to do: native fork
   3. to do: rpc
   4.  ?skip: closure:
      1. it will be close to call with different pid
      2. the implementation still uses the authority server with closures (which could be hacked out)
3. Shared Memory
   1. (ok) Shared Objects: (P) put, get (skip create)
   2. (ok) Shared Queues: enqueue, waitanddequeue: basic + ipc (skip create)
   3. (ok) Shared Locks: Lock, unlock
4. Monster.com: non-aeolus vs. aeolus
   1. complete setup code: adding companies to workers
   2. see if one queue for results works
   3. time basic resume matching
   4. review infoflow control usage

---

1. Skip the following due to rare use
   1. Creation: Normal process creation vs VN creation
   2. Boxes
2. Skip the following due to monster example
   1. (P) Online Store
   2. (P) Secure Wiki
   3. Web: base web service vs. aeolus web service
3. Skip the following: not too interesting
   1. File operations
      1. (P) create dir
      2. (P) create file
      3. (P) list dir
      4. (P) remove file
      5. (P) remove dir
      6. read various size files
      7. write various size files
      8. file stream open and read, various size files
      9. file stream write, various size files
      10. Note: the paper mentions some measurement information about accessing file content
   2. Authority Server