Comments for Code, Life and Learning

Comment on Building a scalable, fault tolerant background processing system (part 2) by viewmessages.com Architecture « Code, Life and Learning

viewmessages.com Architecture « Code, Life and Learning — Fri, 30 Jul 2010 18:03:59 +0000

[...] The back end task processing is something I’m particularly pleased with as it allows the processing load to be distributed across as many machines as we need. At the moment these are the same machines that serve the front end web stuff but at a later date will be split off into a dedicated back end cluster. All the back end processing is done by requesting webpages from a queue. If you want to read about how we process background tasks heres my blog post about it [...]

Comment on Shared file storage on a web cluster. by viewmessages.com Architecture « Code, Life and Learning

viewmessages.com Architecture « Code, Life and Learning — Fri, 30 Jul 2010 17:15:29 +0000

[...] Because we use a web cluster to serve the main HTML we need a central server for avatars and other central data that we don’t push to Cloudfront. The only challenge here was getting content to it. Security in IIS from the main webcluster meant I couldn’t access the machine directly to I had to use a SQL database as a proxy [...]

Comment on Distributed Caching Showdown – Memcached vs Velocity by viewmessages.com Architecture « Code, Life and Learning

viewmessages.com Architecture « Code, Life and Learning — Fri, 30 Jul 2010 17:10:21 +0000

[...] And to think, I was almost tempted to use Velocity instead. You can read why I didn’t. [...]

Comment on Project Totem – A Long Polling server (Part 1) by viewmessages.com Architecture « Code, Life and Learning

viewmessages.com Architecture « Code, Life and Learning — Fri, 30 Jul 2010 17:09:57 +0000

[...] the response to the original request that was made 5 seconds previously. For more on Totem, read my Project Totem blog [...]

Comment on Re-inventing the spell checker by Andrew Falkingbridge

Andrew Falkingbridge — Wed, 05 May 2010 17:31:07 +0000

Very interesting approach. How did you arrive at the weightings – have you tried tweaking them? Also some opportunity here to introduce a naive Bayes classifier to make educated guesses on the 3 word tuples? And how about looking to correct grammar as well as spelling – so that you don’t get “a lot” written in such a way it refers to the mythical beast?

Comment on Making the ‘New Message Alert’ slicker with jQuery AJAX by James

James — Fri, 13 Nov 2009 10:30:25 +0000

makes perfect sense to me

Comment on Who needs values these days? by Tim Skipper

Tim Skipper — Fri, 07 Aug 2009 07:36:50 +0000

Hey Brian! I found this post quite by random and as it happens I’m having the *exact same* issue with paramterised queries running madly slow compared to a straight SQL query, at one of my client sites.

I’m going to get my devs to go pull the code and see if it’s the same param type issue.

Thanks for the post! (and congrats, by the way)

Tim.

Comment on Partitioning Data in SQL by Phillip Abbott

Phillip Abbott — Mon, 27 Jul 2009 21:58:26 +0000

Is it better to have one large table or lots of little ones? Given both options wouldn’t differ that greatly in space usage what are the advantages of splitting data out? I can only really see the increased dependencies and complexity between your code and your data. Add in multiple indexes on each table and it all sounds exponentially more difficult to maintain.

Comment on Partitioning Data in SQL by Andrew

Andrew — Fri, 17 Jul 2009 18:14:02 +0000

What are you trying to achieve?

Would be better to do in SQL rather than ASP?

Have a table of Companies
With some fields of: CompanyName, CompanyID (as GUID)

The CompanyID then is your hash function (good enough for these purposes)

Then when a new company is added use ASP or StoredProc to allocate the next free DB / Table combo (using simple counters from a reference data table).

Then when doing the select do two pre-selects to get the Table and DB for the CustomerGUID in question.

Concatenate these into the SELECT statements.

Done.

But I still don’t know what you are trying to achieve. SQL can work very well on humongous data sets. Take a look at query analyzer and tuning tools (y)

Comment on Every guy needs a picture of a rocketship on his wall. by Andrew

Andrew — Thu, 16 Jul 2009 17:21:52 +0000

Brilliant pic, I might have to order a copy. I don’t recall a gift shop when I was there, otherwise the plastic would have taken a hit! I like your musings too.