scaling

I am trying to create a higher resolution image of a UIView , specifically UITextView . This question and answer is exactly what I am trying to figure out: Retain the resolution of the label after scaling in iphone But, when I do the same, my text is still blurry: self.view.transform = CGAffineTransformMakeScale(2.f, 2.f); [myText setContentScaleFactor:2.f]; // myText is a subview of self.view object I have also tried the same in the Apple sample project "UICatalog" to UILabel and it is also blurry. I can't understand why it would work for Warrior from the other question and not for me. I

The attached simple Java code should load all available cpu core when starting it with the right parameters. So for instance, you start it with java VMTest 8 int 0 and it will start 8 threads that do nothing else than looping and adding 2 to an integer. Something that runs in registers and not even allocates new memory. The problem we are facing now is, that we do not get a 24 core machine loaded (AMD 2 sockets with 12 cores each), when running this simple program (with 24 threads of course). Similar things happen with 2 programs each 12 threads or smaller machines. So our suspicion is that

I am writing some code that uses HTML5 canvas. Generally it works well, but now I found a very strange behaviour. The weird thing is that it is consistent on different browsers, so must be that I understood the thing wrong... Despite the docs seem to say exactly what I am doing. Here is the code (it's an object method): MyCanvas.prototype.getElement = function() { var innerHtml = "<div></div>"; var elem = jQuery(innerHtml, { 'id' : this.viewId }); var canvas = jQuery("<canvas/>", { 'id' : this.viewId + "canvas", 'width' : this.width, 'height' : this.height }); var w = this.width; var h = this

I want to know if there are any good solutions for autoscaling dynos AND workers on Heroku in a production environment (probably a different solution for each of those, as they are pretty unrelated). What are you/companies using, regarding this? I found lots of options, but none of them seem really mature for a production environment. There is Heroscale, which seem to introduce some latency as it does not run locally, and I also heard of some downtime. There are modifications of delayed_jobs, which have not been updated for a long time, and there are some issues with current bundlers. There is

I am putting together a REST API and as I'm unsure how it will scale or what the demand for it will be, I'd like to be able to rate limit uses of it as well as to be able to temporarily refuse requests when the box is over capacity or if there is some kind of slashdotted scenario. I'd also like to be able to gracefully bring the service down temporarily (while giving clients results that indicate the main service is offline for a bit) when/if I need to scale the service by adding more capacity. Are there any best practices for this kind of thing? Implementation is Rails with mysql. temoto This

I know that horizontal partitioning...you can create many tables. How can you do this with multiple servers? This will allow Mysql to scale. Create X tables on X servers? Does anyone care to explain, or have a good beginner's tutorial (step-by-step) that teaches you how to partition across multiple servers? With MySQL, people generally do what is called application based sharding . In a nutshell, you will have the same database structure on multiple database servers. But it won't contain the same data. So for example: Users 1 - 10000: server A Users 10001 - 20000: server B Sharding (of course)