I also think it’s interesting thinking about building a client library across multiple languages and how your thoughts about the API methods might change. Think that would have any impact?

I haven’t used Bugzilla since I wrote this blog post in 2008. So, unfortunately, I can’t help.

John

I have installed bugzilla 4.2.1 on centos 6.2 and it is working fine, but when I try to send create new account invitation it will show the following:

A confirmation email has been sent containing a link to continue creating an account. The link will expire if an account is not created within 3 days.

But the client/user is not receiving any bugzilla mail.

Thanks in advance,
Ravindra

Thanks for the comments.

1) The document represents a day in the user’s time zone. The time zone in the “date” field is not used. So, the user is stuck with this timezone, but not forever. The summary documents summarize data that is stored in our MySQL database. If necessary, we can always rebuild them for a user based on a new time zone.

2) The 502ms is for the full HTTP request, and not just the database query. I don’t have the breakdown, but I don’t think MongoDB was a big part of that time. I think much of it was spent in Ruby/Rails code (we fetch the documents from MongoDB, and then sum the data using Ruby code), and the HTTP request in general. If I’m able to track down the breakdown of that request, I’ll post it here.

1) Since you’re summarizing daily, does that mean you just pick a timezone and stick with it forever? In the code sample it looks like you’re using UTC, but you’re based in the US. Is it an issue to people looking at the reports that the “days” are 6-8 hours off of what they might be expecting? (This is something I’m trying to plan around).

2) Maybe I’ve misread the conclusion, but if it takes on the order of a half a second to run a report that’s querying 30 rows, that still seems about an order of magnitude too slow, no? At least, coming from a relational background, I would expect this to be a tens-of and not hundreds-of millisecond operation. Do you think this this because you wound up having to do the summations post-facto, Ruby?

Thanks again for sharing the article.

Also, I know you’re interested mobile optimization of applications – something we’re focusing on heavily this year. I think there will be a treasure trove of projects there that’ll get you excited.

I agree that practice doesn’t make perfect, but perfect practice isn’t necessary (or sufficient) either. It takes practice and reflection. This is exactly what you did at that retreat: practice, then think about how you did it, what you did well, what you could do better. Devoting a portion of our mind during practice to recording what we’re doing, and then reviewing and reflecting on those observations and the results later — that’s how we get better.

Practice and reflection! it’s my motto. (one of many)

We’ll be having another one on the day after the Software Craftsmanship North America conference. Look for the registration to go up sometime soon.

http://www.mongodb.org/display/DOCS/Production+Deployments

Thanks!

If you use the query option to the mapreduce command it will be able to use the index to filter the objects to map over. However if you do the selection in your map function with an if statement then that can’t use an index. Either way for 365 smallish docs, it will still probably be faster to process client-side anyway, especially if you make good use of the second argument to find.

I created this patch while using bugzilla 3.0. It looks like SMTP authentication was added in the 3.2.x release (http://www.bugzilla.org/releases/4.0/release-notes.html#v40_feat). So, you should not need this patch for version 4.0 of bugzilla.