Interesting. That sounds super complicated. I was wondering from the start why you didn't just cache rendered resumes. After all, I think resumes tend to be static on the scale of hours even for active jobseekers. So then I got to the end and it sounds like you're caching renders in S3. I must be missing something. I have no experience with SVG on the web apart from playing with Raphael, so could you help me understand why simple caching was not enough? On Apr 28, 2012 6:28 AM, "Ilya Gindin" <[email protected]> wrote:
> Hi everyone, we (ResumUP.com) have a short story, that might be > interesting for you, this story of suffering, pain, success and failures in > an attempt to speed up RaphaelJS on big and complex SVGs. > > Read a full post in our team blog: > > http://ring.resumup.com/ > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
