Improved parallelization of CPU-intensive tasks, Part II
OK, we're back!
As I mentioned in the previous post (published on February 9th), here at Spin Rewriter we always strive to further improve our server infrastructure and fine-tune our code. We're looking to deliver faster and better software that's more intuitive and more robust than ever before.
We've now taken advantage of some new opportunities to parallelize certain aspects of Spin Rewriter's existing spinning process. This means that we're now able to run certain parts of the spinning process on multiple processors (CPUs) on different servers at the same time instead of running it on just one server.
Here's a simplified explanation of the benefits this brings. Imagine you have an article with 20 sentences. We can either have our software detect the parts-of-speech on each of those sentences in a row, and if it takes our software one second to analyze every sentence, we're looking at 20 x 1 second = 20 seconds of waiting time for the user.
We can, however, break this article down into 20 separate sentences — and send each of these sentences to a different server in our grid at the same time. Each of those 20 servers then processes just one sentence, and only 1 second later we get the processed results back to the central system.
The result: The same article is now fully processed in just 1 second instead of 20.
And the result that matters much more than that: Our users are even happier! 😃
Of course the exact real-world situation isn't as cut and dry, but we were still able to roll out a significant improvement in speed and robustness of our spinning systems — and we hope you'll love it!
As I mentioned in the previous post (published on February 9th), here at Spin Rewriter we always strive to further improve our server infrastructure and fine-tune our code. We're looking to deliver faster and better software that's more intuitive and more robust than ever before.
We've now taken advantage of some new opportunities to parallelize certain aspects of Spin Rewriter's existing spinning process. This means that we're now able to run certain parts of the spinning process on multiple processors (CPUs) on different servers at the same time instead of running it on just one server.
Here's a simplified explanation of the benefits this brings. Imagine you have an article with 20 sentences. We can either have our software detect the parts-of-speech on each of those sentences in a row, and if it takes our software one second to analyze every sentence, we're looking at 20 x 1 second = 20 seconds of waiting time for the user.
We can, however, break this article down into 20 separate sentences — and send each of these sentences to a different server in our grid at the same time. Each of those 20 servers then processes just one sentence, and only 1 second later we get the processed results back to the central system.
The result: The same article is now fully processed in just 1 second instead of 20.
And the result that matters much more than that: Our users are even happier! 😃
Of course the exact real-world situation isn't as cut and dry, but we were still able to roll out a significant improvement in speed and robustness of our spinning systems — and we hope you'll love it!
Improved parallelization of CPU-intensive tasks
OK, the title of this post might sound a bit "high and mighty", but hopefully it shouldn't be too difficult to understand once we break it down a bit.
As you probably already know, our server infrastructure is quite state-of-the-art which allows Spin Rewriter to have great uptime and to always process all of your articles, find the best synonyms, manipulate sentence structures, export thousands of text files etc. etc. in a matter of seconds.
We always strive to further improve our infrastructure and our back-end software code. Faster, better, more intuitive, more robust — this is what drives us.
We've recently dug extra deeply into our software and found some new opportunities to parallelize some aspects of the spinning process. In other words, we're now able to run a certain aspect of the spinning process on multiple processors (CPUs) on different servers at the same time instead of running it on just one server.
We'll bring you more details in our next post, however right now we can already give you a hint that GREAT things are underway. Stay tuned! 😃
As you probably already know, our server infrastructure is quite state-of-the-art which allows Spin Rewriter to have great uptime and to always process all of your articles, find the best synonyms, manipulate sentence structures, export thousands of text files etc. etc. in a matter of seconds.
We always strive to further improve our infrastructure and our back-end software code. Faster, better, more intuitive, more robust — this is what drives us.
We've recently dug extra deeply into our software and found some new opportunities to parallelize some aspects of the spinning process. In other words, we're now able to run a certain aspect of the spinning process on multiple processors (CPUs) on different servers at the same time instead of running it on just one server.
We'll bring you more details in our next post, however right now we can already give you a hint that GREAT things are underway. Stay tuned! 😃
For more posts, check out the Monthly Archives.
Our blog posts let our users stay up-to-date with all of the updates here at Spin Rewriter. This way you can discover all of the latest features — so you can try them out and tell us what you think.
We really appreciate all of your feedback — thank you!
