Its good to mention also that the same site is serve by Monkey

My car:

• Kia Sportage GE ’97 (made in America)
• Failure: flywheel

This is my flywheel:

the Flywheel have two sides, one with teeths and the other with a small squares. My teeth side is almost broken so i need to change the whole part, Googling a bit i found some vendors from the US that can ship the replacement but no one is able to confirm if the part is about both sides or just one of them. Its a very old car so they do not have full specs about each part.

Would you please point me to the right vendor  to purchase the whole part ?, any help is appreciated.

Your Organization Application for “Monkey HTTP Daemon” in
Google Summer of Code 2012 has been accepted.

Today begins a new stage for our project, after thousands of work hours and many years putting our best effort, we are finally being recognized internationally as a strong community with serious objectives and delivering a high quality product. This is a great opportunity to grow in different aspects of the project: organization, community and software improvement.

We invite to any student around the world to apply for our organization, we are committed to improve the server side of the web, we deal with embedded devices, performance, scalability, networking, and many cool stuff , innovation is one of our primary focus. Please review our project ideas site:

• http://monkey-project.com/gsoc2012/ideas

If you think that the web can still be improved, we are in the same page and we are looking to hear from you, meet us on irc.freenode.net #monkey or through our mailing list

There is one fact: we are in exciting times for the project. Our HTTP core is consolidated since a while ago, it works in non-blocking mode, it has a nice indented configuration model and provide an advanced API to extend the core behavior, through this we support different behaviors by layers like IPv4, IPv6, SSL encription, security by subnets, basic auth, shell, log writer, etc.

There is a common question from people around the project: “where are you going ?” and the answer is: do you see that embedded Linux Box ?, there’s where we go. Common web servers lack of performance for embedded systems, most of them have focused in high production environments. our focus is different.

Our tech world is service oriented and i would say that implemented through a fat HTTP software stack, simple things are done in scripting languages that requires a process context or even be ran in a JVM environment, that is not lightweight and requires extra resources to be scalable. If you plan to implement a web service for embedded you should start forgetting about Java and PHP and think in lightweight options. Please Google a little about the options available and then continue reading here.

I am pleased to announce Duda, a web services framework built on top of Monkey, is event-driven oriented and expose a friendly C API for the implementation of web services. It goals are performance and easy deployment. It target Linux embedded devices based on ARM (x86 and x64). It implementations is licensed under the LGPL so it allows to link your private web service with our GPL product.

Duda stack overview

There are many mechanisms to achieve a great performance, but talking in an embedded context the primary answer will be: do it in C. Duda and it’s API is made for C developers looking for an event-driven framework supporting URI maps and callbacks. We define an URI map as follows:

/webservice_name/interface/method/param_1/param_2/param_N

• webservice_name: the web service name, a short name like ‘myapp’
• interface: an interface group a set of methods, think it like a main class, mostly for ordering purposes.
• method: a routine who take cares of the main request, this is mapped internally by a callback and is able to send response data
• param: parameters passed through the URI, it’s limited to 16 parameters per request.

If you desire to pass a huge amount of data, you can consider using the POST HTTP method, Duda supports JSON in case you wanted to use it.

Performance: Duda v/s NodeJS

Now how we compare Duda versus the NodeJS framework ?: Duda is for C developers looking for achieve performance with low resources usage, NodeJS is for javascript developers who wanted to write server side implementations. You could claim that NodeJS is pretty faster compared to Apache.. and let me tell you that any non-blocking implementation will be faster than Apache, but.. could be a Javascript engine be faster than something written in C ?, the answer is NO. You can great things with NodeJS, but this last one is not the ultimate solution.

For the following tests i have created a NodeJS script with 5 workers (same as monkey) which replies a “Hello World!\n” string (13 bytes)

Requests per second

I have done the easiest bechmark test with Apache benchmark: 50000 request with 100 concurrents hitting the hello world of each server:

Duda + Monkey is 24% faster than NodeJS

Total transferred bytes

Something is wrong here, why Monkey transferred almost twice bytes than NodeJS ?, looking at the response header we can see that NodeJS is being tricky, its not sending the HTTP Date header, i expected the framework do this by its own.

Duda + Monkey sent twice of data and we continue being faster

Memory Usage

Its importan to know how much memory is using each service when is running, check the results and

Duda + Monkey only uses 264KB while NodeJS requires 35MB

A graphical comparison of Memory usage:

35MB isn't too much ?

Conclusion

Duda since it’s beginning is hitting a huge performance, is ready for embedded due to it lightweight nature. We are hard working to implement required features such as Redis, Memcache, MySQL and others. All of this is part of Monkey v1.0 so stay tuned. We keep rocking, and now harder

[UPDATE]

• You can get the Apache Benchmark results and code for each services from here

When you are a child your imagination does not have limits, when you grow you are instructed to limit the scope of your imagination to what you just have to learn, i do not say that teaching is bad, i say that the knowledge must be share but also people should be inspired to be connected  with the “creativity”, I consider the creativity a state of collective conscience where everything already exists, when you “create something” you are just being able to pick up a piece of that conscience, commonly named an “idea”.

Also if we see how we commonly work i would describe two scenarios: people working in a company and people working by their own. When you work for a company you are mostly working in the other person dreams, at least you share the same vision and feel part of what is being done. For people doing their own stuff  or working as independent, they are trying to reach their dreams. There is nothing wrong with the mentioned scenarios, except when you do not share the same vision or you are not able to “create” due to “limits” imposed.

Said that, i can conclude that the main problem is the education model, because you are educated about how to think, what to accept and then what to do to work. Would not be a coincidence that some successful people in the tech area broke their traditional educational model and then were able to create great things ?: Steve Jobs, Bill Gates, Mark Zuckerberg.. no one of them continue their studies, they just took ideas, connected points, imagine an improved work scenario, connected people.. etc.  I do not know if they were or are happy, but i am sure that they are satisfied with their archived goals…

Talking about educational models I cannot omit to mention One Laptop Per Child project, just to reminder it is not about cheap laptops, it is about access to the information and have an extra tool to help to explore and create.. you should review the success of this project with children in different countries…leave them a time alone and you will realize the amazing things that they do…

As this is just “my truth, I would suggest to watch the following videos, get your own conclusions:

• Ken Robinson – Changing Paradigms
• Tom Preston Werner – Optimizing for Happiness
• Steven Johnson – Where good ideas come from ?

This is not just about do what you want to do, it is about to wake up your conscience and listen your self… we can do something better for our kids and our selfs…

Entrepreneurship

• Lean Launchpad
• Technology Entrepreneurship

Civil Engineering

• Making Green Buildings

Electrical Engineering

• Information Theory

Computer Science

• CS 101
• Machine Learning
• Software as a Service
• Human-Computer Interaction
• Natural Language Processing
• Game Theory
• Probabilistic Graphical Models
• Cryptography
• Design and Analysis of Algorithms I

FTDI Interface

After doing minor tweaks to the chumby-oe project, get some help from Guy Carpenter (thanks!) and fix some bitbake files, i managed to create a new bootable image with Wifi support (i mention this because the Marvel wifi chip requires some specific firmware files)

Infocast 8 booting Angstrom Linux Kernel

Now connect to the Wifi AP is a little tricky, you need to set something in the following order:

# iwpriv mlan0 setregioncode 0×10
# ifconfig mlan0 up
# iwconfig mlan0 mode managed
# iwconfig mlan0 key YOUR_WEP_KEY
# iwconfig mlan0 key on
# iwconfig mlan0 essid YOUR_ESSID
# udhcpc -i mlan0

After that you will be able to connect to your AP and have network access.

You can download the ROM image from here, or if you prefer, you can browse the whole content. Once you get the ROM image you need to burn it into the internal 2G SD Card, you can do it with: dd if=rom-chumby-silvermoon-chumby-starter-image.img of=/dev/sdX bs=8M. Make sure before to run the dd command, do a manual umount for each partition.

I did not know too much about NodeJS, so i dedicated some time to read the documentation and papers available, so being a web server side guy i would like to share my opinion, because i listen too much about that everybody must move to NodeJS.

The primary feature of NodeJS is that provides a framework  based in a language thats handled by thousands of people: Javascript, if you are a real web developer you know what is JavaScript and you know how to deal with it, so you can jump directly from the client to the server side and write your own implementation, based on an event driven infrastructure with reduced I/O and better performance than dynamic content generators available such as Ruby, Python or PHP.  It’s pretty interesting as technology which expose new possibilities to improve backend sides, but you must know when and where to use it.

The good thing is that Node abstract you from the dirty low level concepts of a web server like threading, shared memory, asynchronous sockets, reduced I/O, etc. But this have a cost, this is not magic, is just cool, because it works and have demonstrated to perform very well and have a level of trust as is written on top of V8 JavaScript engine supported by Google. The cost of an event driven solution is that if for some reason the program have an exception, the whole service will block or even crash depending of the case, so you must be aware because if something similar happen. As an example, if some Apache context fails, it will kill the process or thread and start a new one, which is not the case of a common event driven web server. What happen if you have 1000 connections transferring data and the program fail ?, it will be critical, and this things happens when working in high production environment, if you have 50 requests per day you are safe and you can stop reading now

Node fills fine if you have thousands of incoming connections and your computing time is reduced, but if you will work with some complexity querying a database, doing some memcache or similar, you should start considering different options.

From now i start talking about solutions for really higher performance, Node is fast, but you cannot compare it with Apache, because Apache is the slowest web server available, compare it with NginX or Monkey. I will do a test now using the Apache Benchmark Utility comparing the NodeJS hello world example against Monkey which will serve a file which contains the Hello World message, the benchmark utility will perform 100.000 requests through 5000 concurrent connections.

NodeJS Benchmark

edsiper@monotop:/home/edsiper/# ab -n 100000 -c 5000 http://localhost:8888/
This is ApacheBench, Version 2.3 <$Revision: 655654 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/
Benchmarking localhost (be patient)

Completed 10000 requests
Completed 20000 requests
Completed 30000 requests
Completed 40000 requests
Completed 50000 requests
Completed 60000 requests
Completed 70000 requests
Completed 80000 requests
Completed 90000 requests
Completed 100000 requests
Finished 100000 requests

Server Software:
Server Hostname:        localhost
Server Port:            8888
Document Path:          /
Document Length:        11 bytes

Concurrency Level: 5000
Time taken for tests: 9.403 seconds
Complete requests: 99747
Failed requests: 0
Write errors: 0
Total transferred: 7481025 bytes
HTML transferred: 1097217 bytes
Requests per second: 10608.48 [#/sec] (mean)
Time per request: 471.321 [ms] (mean)
Time per request: 0.094 [ms] (mean, across all concurrent requests)
Transfer rate: 776.99 [Kbytes/sec] received

 

The NodeJS server was capable to serve 10608 requests per second and took 9 seconds to serve the 100.000 requests. Now let’s see how Monkey did…

Monkey HTTP Daemon Benchmark

edsiper@monotop:/home/edsiper/# ab -n 100000 -c 5000 http://localhost:2001/h.txt
This is ApacheBench, Version 2.3 <$Revision: 655654 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/
Benchmarking localhost (be patient)

Completed 10000 requests
Completed 20000 requests
Completed 30000 requests
Completed 40000 requests
Completed 50000 requests
Completed 60000 requests
Completed 70000 requests
Completed 80000 requests
Completed 90000 requests
Completed 100000 requests
Finished 100000 requests

Server Software:        Monkey/0.30.0
Server Hostname:        localhost
Server Port:            2001
Document Path:          /h.txt
Document Length:        13 bytes
Concurrency Level:      5000
Time taken for tests:   5.718 seconds
Complete requests:      100000
Failed requests:        0
Write errors:           0
Total transferred:      20300000 bytes
HTML transferred:       1300000 bytes
Requests per second:    17489.54 [#/sec] (mean)
Time per request:       285.885 [ms] (mean)
Time per request:       0.057 [ms] (mean, across all concurrent requests)
Transfer rate:          3467.16 [Kbytes/sec] received

Monkey did 17.489 requests per second and took 5.7 seconds to serve the 100.000 requests. Ooops!

The impressive results are even better, because Monkey performed 100.000 I/O to retrieve a file from the hard disk and also send a couple of extra bytes one each response (Monkey does not cache file contents or metadata). Serve a file is a slow process due to I/O, so i will do a test later with the same case serving some fixed content through a plugin (something similar to what Node is doing in the test example).

What am trying to say here, is that depending of what are you trying to accomplish and the complexity of your backend., NodeJS can be the solution for your environment as well you could need something even more scalable like Monkey, but the learning curve of NodeJS is short and the learning curve of Monkey is a little high, but this last one  provides a better performance because all is well written in C, as well any extension through the C API interface requires some knowledge which in NodeJS are hidden, you have to balance between goals, knowledge, learning curve and deadlines.

[UPDATE]:

• Joe provide me a new code to launch Node with multiple workers, so Node increase the performance, the new values were updated.

The psychical place where the event was done, was in the Santa Maria University in Santiago, the chosen place was really nice, 1 big conference room which split in 3 parts for later hold the parallel track sessions. Outside of the conference room, exists a ground where you can talk with each other, take some sun (others a nap), lunch and maybe drink some beer (will describe above).

There were different teams helping to develop the event, i can remember people from the following teams: Security, Support, Presenters, Personal assistance (for international speakers who do not speak Spanish)..etc.  I would count no less than 120 people helping on this, so the event was something big. Just to mention that when i arrive the past Friday in the morning there were about 600 attendances and then after the accreditation…about 800.

I met very nice speakers, like Caridy Patino (Yahoo Senior Search Engineer), Charles Nutter (leader of JRuby), Stephanie Rewis (Founder of W3Conversions), Mark Ramm (Technical leader at Sourceforge.net), Jano Gonzalez (Continuum Developer), Hannu Krosing (PostgreSQL hacker) and Tomas Pollak (creator of Prey Project). All speakers were very open and nicely, some of them dedicated a lot of time to talk with the attendances and get involved in different activities around the event, which is really good for all attendances, is not common that the whole events the speakers dedicate some time to talk to everyone (even drink a beer).

I went to a couple of sessions and i would like to remark four of them: Caridy talked about how are they implementing Node.JS in Yahoo, before the talk we discussed a lot of what Node.JS is and where is going… seems like a strong competitor for web services is already around and positioning in huge production environments. The talk was pretty good, covering different details about business requirements and technical stuff as solutions. Stephanie (who opened the event, gave the first key note), talked about CSS3 ( i have to admit that i am not a fan of CSS, HTML, i use them… but well..), she gave a master class of new features of CSS3 and tips to provide nice user interfaces, as well how to deal with different browsers. Scott Chacon (author of ProGit book, and VP of GitHub) gave an excellent speak about GIT with focus in trees and the reset command, very nice slides and well done presentation. And i would consider the talk of Tom Preston-Werner (GitHub CTO) the one with a huge personal impact to me. He talked about optimizing for happiness in your daily job, and how the external and internal motivators act directly in benefit of your happiness (or maybe not). I felt very identified when he described a simple example: you go to the office, you do your work, back home and then you work (or hack) your personal projects, and i have to admit that… i am that guy.

The non-technical part, was really impressive that sponsor companies provided free beer for all attendances after each session day!, the two days ended with a beer party in the ground, this is not common, trust me, and is very valuable!, not just for the free beer, just for a different context where all attendances (including speakers and organization) could interact in a different way and relax. Also i can not omit to mention the effort putted by Movistar and (specially) Microsoft to make than more than 800 hackers disconnect from their laptops or geek devices to enjoy something different, if you attended the event you know what i am referring to

This is the first time that i do not see any bad points in a conference, the organization did an excellent work, sometimes they look tired but always moving on, putting all their energies to have a successful event and it was. i just say THANK YOU! for have the opportunity to be part of this and enjoy a nice two days event.

I am sure that Startechconf 2012 is something that’s coming, and i cannot imagine how it could be better than the first version. If you could not attend this year, please consider to prepare for the next one, because it will rock!

This Friday and Saturday (Nov 4th – 5th), Monkey Project will be present at the Startechconf.com, we will give a talk about the project goals, internals and current features. We are preparing a really nice presentation, including a few presents for the lucky attendances.

Do not forget to follow us at @monkeywebserver