View Single Post
  #89   Spotlight this post!  
Unread 23-11-2013, 02:07
1306scouting 1306scouting is offline
Registered User
FRC #1306 (BadgerB.O.T.S.)
Team Role: Scout
 
Join Date: Apr 2012
Rookie Year: 2004
Location: Madison, WI
Posts: 24
1306scouting is on a distinguished road
Re: A New Way to Scout

Quote:
Originally Posted by yash101 View Post
With HTML5, you get drag n drop! So, record the position of robot shoot point(s) and store them in a database.

After thinking for a lot of time, I was thinking about which Database I should use. My hosting platform is a Raspberry Pi, so I do not have too much power. What database should I use for such an intensive application?
The issue is for teams like mine that scout on paper sheets - there's no reasonable way to encode where the shots are coming from on a piece of paper (though I think OMAR, our scan-reading software, could probably do it if we wanted it to).

(Warning: speculation ahead, I could be wrong about this: )

Honestly, a Raspberry Pi doesn't have nearly enough power to run this scale an application. You need a lot more RAM for DBs; the 512MB on the Raspberry Pi probably won't be enough, I'd want at least 2-4GB for this size of database with the amount of data that we could be working with. Part of that is me wanting plenty extra for comfort, since the database may be able to run in 512MB, but part is the fact that I use more than 512MB while my web servers are idle on my personal server (admittedly not heavily optimized, but also not nearly as intensive as the sort of database we'll be using.)

Last edited by 1306scouting : 23-11-2013 at 02:17. Reason: Clarify speculation