» tagged pages
» logout

(Feed found, click Add Page to syndicate.) Error finding feed, please try again » Find feed title

A Blog Page allows you to add entries, for news or other time sensitive postings

(Login required to save to your tagged pages.)
(or Cancel)

Make further edits, (or Cancel)

(Login required to save to your tagged pages.)
(or Cancel)

(Editing anonymously: to be credited for your changes, login or register a new account)

Change Page Permissions? Changing these permissions will adjust who can modify this page.

bollin (change)
Swik Users (change)
(or Cancel)
Upload an image from your computer:
or Copy an image from a URL:
or Erase the current icon:
Icon Preview:

or Cancel

Erase Sphinx? The contents of Sphinx page and all pages directly attached to Sphinx will be erased.

or Cancel

(Editing anonymously: to be credited for your changes, login or register a new account)

other page actions:
Sphinx

CMU Sphinx Group Open Source Speech Recognition Engines

Sphinx Wiki Pages

The Sphinx Group at Carnegie Mellon University is committed to releasing the long-time, DARPA-funded Sphinx projects widely, in order to stimulate the creation of speech-using tools and applications, and to advance the state of the art both directly in speech recognition, as well as in related areas including dialog systems and speech synthesis.

,

sorted by: recent | see : popular
Content Tagged Sphinx

MichiPUG meeting on Thursday, April 3

The Michigan Python Users Group (MichiPUG) monthly meeting is coming up on Thursday, April 3.

We’ve got two exciting topics for this month’s meeting. The first part is Mark Ramm leading some discussion on documentation tools (including Sphinx). I roped Mark into this because I haven’t yet run Sphinx, but it looks great. He’ll also talk about Idiopidae which Zed Shaw and Mark were hacking on at PyCon.

I’ll also lead some discussion and experimentation with EasyExtend, Kay Schluehr’s tool for monkeying with Python’s syntax.

Should be a fun time, and I hope to see you there!

TurboGears: TurboGears Blog

Progress on High Performance MySQL, Second Edition

It's been a while since I said anything about the progress on the book. That doesn't mean we are not still working on it, though.

As Peter wrote a while ago, he is basically wearing the hat of a very advanced technical reviewer at this point. We've finished writing all the chapters from his detailed outlines. He has worked through about half the chapters, and I'm continuing to spend my evenings and weekends and holidays (yes, nearly all my free time -- just ask my wife!) writing some new material (an appendix on EXPLAIN, for example), finishing unfinished things marked with TODO in the text, and revising chapters after Peter reviews them. Vadim is working on benchmarks. For example, he just finished some benchmarks for something I profiled with SHOW STATUS. I thought that would be good enough to assert something about the performance. Sure enough, SHOW STATUS says it does less work, but Vadim's benchmarks show it's slower :-) This is why we check each other's work!

The core chapters on MySQL performance -- beginning with Benchmarking and Profiling, and continuing through Optimizing Server Settings -- are the ones Andy Oram, our editor, thinks we should put the most effort into, and I agree. We will probably circle back and go through another review/edit cycle before we release them for technical review. Some of the other chapters, such as Replication, are already out for technical review.

Despite the fact that all of the chapters and appendixes are theoretically a "first draft," as of several weeks ago, there is still a lot of work to do. Depending on the chapter, it takes me a solid weekend to revise a chapter after Peter reviews it. Each little thing anyone points out (does MySQL version X really do Y by default?) requires some research, testing, benchmarks, or even reading the source code.

Some miscellanea:

  • The production staff replied to my inquiry to the editor to say that yes, we will be able to have references that point to a specific page number. This was a big relief to me. It requires extra work, but makes the book so much more valuable as a reference work in my opinion. To see why, look at the top of page 151 in the first section, which just refers to chapters and sections by their titles: "See... the "Tools" section..." Now try to find the "Tools" section. If it took you a while... well, the first time I did it, I missed it, and thought it might mean the Tools Chapter. The second edition will say "The X section on page Y" or similar. (Okay, I'll shut up about this now -- everyone has to have a pet peeve, eh?)
  • We are currently at 425 pages in OpenOffice.org Writer, which by my calculations puts us around 470 pages in print. As I said before, I think we'll break 500 pages by the time we finish the rest of the missing material.
  • Andrew Aksyonoff has contributed an appendix on the Sphinx full-text search system. If you don't know anything about it, check it out. It's an amazing piece of software that does a lot more than just full-text search.

Well, I've run out of my allotted thirty minutes of blogging! Back to the salt mines! Just kidding... I'm actually off to the climbing gym soon to get my mind off it.

MySQL: Planet MySQL

Page 1 | Next >>
Username:
Password:
(or Cancel)