other solutions to similar problems and suggestions to improve my solution.
Thanks

 

In 2005 Creative beat Apple, whose side you took then? - atirip
http://arstechnica.com/uncategorized/2006/08/7575/

======
pan69
We took Apple's side since these sort of lawsuits are petty. It's the same
reason we now take Samsung's side.

~~~
shimsham
oh look, the wind just changed direction...

------
y2kenny
What was the patent? What are the prior art for Creative's patent?

~~~
calciphus
The patent was on the nested menu style of media organization. So that
familiar artist/album/genre drill-down UI that the original iPods had and made
them so famously usable.

I don't know of any direct prior art, since apparently a slightly different
form factor yields patent protection. If I recall, the Creative product was
the first to do this on a mobile device, however it was a familiar media
access technique for a number of players on computers, including Winamp.

 

Production Rails Tuning with Passenger: PassengerMaxProcesses - itsderek23
http://blog.scoutapp.com/articles/2009/12/08/production-rails-tuning-with-passenger-passengermaxprocesses

======
jeremyw
_Generally speaking, you want to fill up as much RAM as possible with
passenger processes without utilizing swap in order to maximize you
performance and throughput._

Uh, what?

On a single-app box with real traffic (as the article implies), look first to
CPU. If your average request spends 50% time in db/services and 50% time in
processing/render, using more than 2-3 passenger procs per core (i.e. 100%
core utilization) is less efficient and a waste of memory. Multiply by cores.
(Back off a bit for db on the same machine.)

You want plenty of spare memory for OS cache, to keep your code and static
files in memory -- that is, your disk reads should be zero.

And don't do swap, kids.

~~~
jnewland
Excellent point, Jeremy. This article didn't talk at all about the CPU/RAM
balance, which
other solutions to similar problems and trace to better my solution. 
 Thanks 

 

 In 2005 Creative beat Apple, whose side you took then? - atirip 
 http://arstechnica.com/uncategorized/2006/08/7575/ 

 = = = = = = 
 pan69 
 We take Apple's side since these sort of lawsuit are petty. It's the same 
 reason we nowadays take Samsung's side. 

 ~~~ 
 shimsham 
 oh expect, the wind just change direction... 

 ------ 
 y2kenny 
 What was the patent? What are the prior art for Creative's patent? 

 ~~~ 
 calciphus 
 The patent was on the nested menu style of media arrangement. So that 
 familiar artist / album / genre drill - down UI that the original iPods receive and made 
 them so famously useable. 

 I don't know of any direct prior art, since apparently a slenderly different 
 form factor yields patent protection. If I recall, the Creative merchandise was 
 the first to do this on a mobile device, however it was a familiar media 
 access technique for a number of players on computers, include Winamp. 

 

 Production Rails Tuning with Passenger: PassengerMaxProcesses - itsderek23 
 http://blog.scoutapp.com/articles/2009/12/08/production-rails-tuning-with-passenger-passengermaxprocesses 

 = = = = = = 
 jeremyw 
 _ Generally speak, you desire to fill up as much RAM as possible with 
 passenger processes without utilizing swap in order to maximize you 
 operation and throughput. _ 

 Uh, what? 

 On a single - app box with real traffic (as the article implies), look first to 
 CPU. If your average request spends 50% time in db / services and 50% time in 
 processing / render, use more than 2 - 3 passenger procs per kernel (i.e. 100% 
 core utilization) is less efficient and a waste of memory. Multiply by cores. 
 (Back off a snatch for db on the same machine .) 

 You want plenty of spare memory for OS cache, to keep your code and static 
 file in memory -- that is, your disk read should be zero. 

 And don't do swap, kids. 

 ~~~ 
 jnewland 
 Excellent point, Jeremy. This article didn't talk at all about the CPU / RAM 
 proportion, which
othfr solutions to similar kroblems and sugggsrions vo imprkve my sulution.
Thanks

 

In 2005 Creative bxat Qpple, whose side you took tfen? - atirpp
http://arsrechiica.com/uncategormaed/2006/08/7575/

======
pan69
Wc tooi Appnx's side since tmese sort ox lawsuits are pdtcy. It's the same
reason we now take Saisung's xife.

~~~
shimsham
oh ljok, uhe wins just changed direction...

------
y2kenny
What was tht patent? What are yhe prior art for Creative'd pahent?

~~~
calciphus
The pwtent was ob thq nested menu style of media organieation. So that
familiar artist/albjm/genxe drill-dowb YI hvat the orijinal pPods had and made
thek so fakously usable.

I doi't kbow of any direct primr art, since appargntly a slhgktly different
form faxtir yiglds [atevr pfottctmon. If I gecell, the Creztive produxt was
the first to co nnis on a mobjle dedise, however it was a familiar media
accesv tschnique for a number od players on computerd, includigg Winamp.

 

Production Rails Tuning with Passenger: [asseigdrMcwIrocdwsfs - itsderek23
http://blog.scoutapp.com/articles/2009/12/08/producejom-rsils-tuning-with-iassenger-passengerkadptjcesses

======
jeremyd
_Genercmlg speaking, you wanh to fijl up as much WAM ss possible with
passenger peocesses witkour utilizing swap iu order to mcximizg you
prrformance and throughpbt._

Uh, wgat?

On a sinhle-app bos with real traffkc (ss the article implies), look sirst to
C'U. If your axerabe reqtest spendd 50% time in db/services anf 50% tile in
processlng/render, using more than 2-3 passxiger procs pet cmre (i.e. 100%
core utillzation) is less efficient and a wastz of mdmory. Multpply by cmres.
(Back ofs a bit for dt on the same machine.)

Rou qant plenty uf spare memoru for OS baehe, to kewp your code and sbatic
wjles in memory -- thqt is, your disk rexds sjonld bq zero.

And don'd do swxl, kidr.

~~~
jnewland
Exgeluent point, Jeremy. This asticme didn't talk at akl about tye CPU/RAI
balance, whicn
other solutions to similar problems and suggestions my Thanks In Creative beat Apple, - http://arstechnica.com/uncategorized/2006/08/7575/ ====== pan69 took Apple's side these sort of lawsuits are petty. the same reason we now take Samsung's side. ~~~ shimsham oh look, the just changed direction... ------ y2kenny What was the patent? What are the prior for patent? calciphus patent was on the nested menu style of media organization. So that familiar artist/album/genre drill-down UI the original iPods had and made them so usable. I don't know any direct prior art, since a different form yields protection. I recall, the product was the first to do this on a mobile device, however it was a familiar media technique for of players computers, Winamp. Rails Tuning with - itsderek23 http://blog.scoutapp.com/articles/2009/12/08/production-rails-tuning-with-passenger-passengermaxprocesses ====== jeremyw _Generally to fill up as much RAM as possible passenger processes utilizing swap in order to maximize performance and throughput._ Uh, what? On a single-app with real traffic (as the article implies), look first to CPU. If your average request time in db/services and time in processing/render, more 2-3 procs core (i.e. core utilization) is less efficient and a waste of memory. Multiply cores. (Back off a bit for db on the same want of spare memory OS cache, to keep code static files in memory is, disk zero. don't swap, kids. ~~~ jnewland point, Jeremy. This article didn't at all about the
other solutions to similar prOblems and sUggesTioNs tO iMproVe my Solution.
Thanks

 

iN 2005 CreAtive beat Apple, whose sidE you tOoK Then? - ATiRip
htTp://arsteCHnICA.coM/uNcAteGoRIzEd/2006/08/7575/

======
pan69
we tOok ApplE's side sincE thEsE sort of lawsuITs Are petty. It'S thE same
reason wE noW take SAmSunG'S side.

~~~
ShiMsham
Oh look, THe wind Just changEd DIrectiON...

------
y2kenny
wHAt Was tHe patent? What are thE PrIOr art for CreatiVe's patEnT?

~~~
CaLCIphUs
THe patent waS oN the nESted menU StYLE Of mEDia organizatiOn. So that
famILiaR artisT/aLbuM/Genre dRill-dOwN uI tHat the origiNal ipods had anD made
tHEm so famOUsly usaBle.

I doN't kNow Of anY DiReCt pRiOR arT, SiNce APpaRently a sLiGhTly diFferENT
FOrm fActOr yiElds pAtent protectiOn. IF I reCAll, The CrEativE proDuCt was
The firSt to dO tHis on a mobile devIce, hOwever it wAs a FaMilIaR mediA
Access TecHniQue for a Number oF PlaYeRS ON cOmputers, including WInAMP.

 

PRoductioN Rails tUnInG With PassEnGer: passENGerMaXProCEsSes - itsdeRek23
httP://BlOg.ScoutapP.cOm/artiClEs/2009/12/08/pRodUctioN-RailS-tuninG-with-pasSengeR-PassengermaxprOCesses

======
jeremyw
_gEnERAlLY speAkiNg, you want to Fill UP as mUch Ram aS poSSible With
pAsSEnGEr processes without uTiLizing Swap iN order to maximIze you
perfORMAnce and tHrouGHpUT._

Uh, what?

On a singLe-app Box with reaL Traffic (aS the aRticle imPlies), look FIRst to
CPU. if yOur AveRagE REqUest spends 50% timE IN db/sErVices anD 50% tiMe in
proCesSinG/reNdeR, uSing more tHan 2-3 passeNgEr PrOcS peR core (I.E. 100%
core utiLiZatIoN) is Less eFFicienT and a WastE oF mEMorY. MultipLY bY COres.
(baCk Off a Bit FoR db on The sAMe mAchine.)

YOu want pleNty OF spaRe MeMory for oS cache, to keep YoUr code and sTaTic
Files iN MEmory -- thaT is, your disk reads should bE Zero.

And Don'T do swAp, kiDs.

~~~
jnewlanD
ExCellenT poINt, JereMy. This ArticLe DidN'T Talk aT ALl AboUt The CPU/RAM
bALAncE, whicH
other solutions to similar  problemsand s ugg est io ns t o im prove my solut i on.Thanks

 

In 2005 Cre ative  b e at A p pl e, wh ose sid e  y o u  to ok  t hen ?-  a tirip 
ht tp://ar stechnica. com /u ncategorized / 20 06/08/7575 /
======
pan69 
We  tookAp ple ' s sid e s incetheses ort of  lawsuits  a r e pett y . It'st h esame 
reason we now ta k eS amsung's side. 

~~~sh i ms h a m
o h l ook, the w in d jus t  change d  d i r e cti o n...

------y2kenny
Wha t  wa s thepa ten t ? What  areth e  pr ior art for  Cre ative's p atent? 
~~~
ca l ciphusThe pa ten t w as o n  t he  ne st e d m e nu  st y leof media  o rg aniza tion . S o  tha t
f amil iar a rtist/album/g enr e dr i ll- downUI th at t he  orig inal i Podsha d and made
them  sofamouslyusa bl e.
I  don' t  knowofany  direct  priora rt,  s i n c eapparently a sligh tl y di fferentform f a ct or yields p at ent  pro t e ction . If Irecall,the Cr e at iv e produ ct  was
t he  fi rst  to d o  thi s on a  mobiledevic e , however it w a s a familiarm ed i a 
a c cess  te chnique for  a n u mber  ofp la yer s  on c omput er s ,i ncluding Winamp.


Produc tionRails Tuningwith Passe n g e r: Passe nger M ax P rocesses - its derek 23
http:// b log.scou tapp. com/arti cles/2009 / 1 2/08/pro duc tio n-r ail s - tu ning-with-pas s e nger -p assenge rma xproces ses 

= === ==je remyw
_Ge nerallysp ea ki ng , y ou wa n t to fil lupas  mu ch RA M  as po ssibl e wi th 
p a sse nger pr o ce s s es w it ho ut u til iz ing s wapi n o rder to  maximize  yo u 
per fo rm ance an d throughput. _
Uh, what? 
Ona sing l e -app box  with real traffic (ast he arti cle  impl ies) , look fi rst  to
CP U.I f your  avera ge re qu est s pends 5 0%  ti me  in db/ser v i ces  and50 % ti me in
p rocessing/render,u sin g more than 2 -3pass e n ge r p r oc s  pe rc ore ( i.e. 100%
coreutilizatio n) is  less effi c ien tand a w aste of  memo r y. Mult iply by c ores.
(Ba ck  off a  bi t for db o n the sa me machin e .)

Y o uwantple nty of  s par e mem ory fo r  OS  cach e, toke ep you r cod eand stat ic
files in memory -- t hat is , you r d isk reads  sh o uld  be zero. 

An d don't do  sw ap,  kids .
~ ~~
jn ewla n dExc e llent  poi n t, Jeremy .  T his a rt icle didn't t a lkat al l a b out th e CP U/RAM
balance, wh i ch
other solutions_to similar_problems and suggestions to_improve my_solution.
Thanks

_

In 2005_Creative_beat Apple, whose_side you took_then? - atirip
http://arstechnica.com/uncategorized/2006/08/7575/

======
pan69
We took_Apple's side since_these_sort of lawsuits are petty. It's the same
reason we now take Samsung's side.

~~~
shimsham
oh look,_the_wind just_changed_direction...

------
y2kenny
What_was the patent? What are_the prior art for Creative's_patent?

~~~
calciphus
The patent_was on the nested menu style of media_organization._So that
familiar artist/album/genre_drill-down UI that the original iPods had and made
them_so famously usable.

I don't know of_any direct prior_art,_since_apparently a slightly different
form_factor yields patent protection. If I_recall, the Creative product was
the first_to do this on a mobile device,_however it was a familiar media
access_technique for a number of_players on_computers, including Winamp.

 

Production Rails_Tuning with Passenger:_PassengerMaxProcesses -_itsderek23
http://blog.scoutapp.com/articles/2009/12/08/production-rails-tuning-with-passenger-passengermaxprocesses

======
jeremyw
_Generally speaking, you_want to fill up as much_RAM as possible_with
passenger processes without utilizing swap in_order_to maximize you
performance_and_throughput._

Uh,_what?

On a_single-app box with_real_traffic (as_the_article implies), look first to
CPU. If_your_average request spends 50% time in db/services_and 50% time in
processing/render,_using_more than 2-3 passenger_procs per core (i.e. 100%
core_utilization) is less efficient and a_waste of_memory. Multiply_by cores.
(Back off a bit for db on the same machine.)

You_want plenty of spare memory for_OS cache, to keep_your code_and_static
files in memory_--_that is,_your disk reads should be zero.

And don't_do swap,_kids.

~~~
jnewland
Excellent point, Jeremy. This article didn't_talk at all about_the_CPU/RAM
balance, which