tweelter
Successor to cloud computing, aka tweelter new architecture
Wednesday, January 20th, 2010 | Web | Comments
When you have to perform a real big amount of operations you have two options
- Increase your computational power (like using a cloud solution or scale on more servers)
- Move your computations to the most available cloud platform of the world: your users
To improve tweelter performances and avoid overloading twitter API we are studying a new computational architecture for tweelter which can return results to the user faster and give less overhead to our servers.
The key to achieve the result is to move most of the search overhead to the computers of the other users currently viewing tweelter, like SETI@home does, by using tweelter you would speed up other users searches and also your own searches.
Search
Archives
- January 2012
- November 2011
- October 2011
- July 2011
- June 2011
- May 2011
- April 2011
- March 2011
- February 2011
- January 2011
- December 2010
- November 2010
- September 2010
- August 2010
- July 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- December 2008
- November 2008
- October 2008
- August 2008
Tags
3D
acr
apache
automake
autotools
benchmarks
callgrind
canvas
centos
cms
efika
elixir
functional programming
gentoo
gluster
google
labs
libacr
Linux
modsecurity
mongodb
netbook
oprofile
osx
pyhp
python
ragel
rails
redis
repoze.who
review
ruby
security
sprox
sqlalchemy
ssd
Streaming
toscawidgets
turbogears
turbogears2
twitter
valgrind
Web
webserver
windows