You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
-
1A problem is required to be (a) parallelisable and (b) have well-defined standards to be considered for or benefit from dedicated hardware (such as a GPU). Text search can be broken down into smaller parts as long as the target is large. Most other operations that you've mentioned can't - streaming the output is as difficult as the operation involved.Ordous– Ordous2014-12-08 20:57:23 +00:00Commented Dec 8, 2014 at 20:57
-
2a good overview on FPGA's and their applicability to stream processing can be found here, which could be extended to text processing, I guess. However, text processing often involves frequency counting of words and phrases, as well as indexing, which I doubt is more efficient if done at the hardware level. Except if your inputs are known beforehand, which kind of defeats the purpose of text processing.miraculixx– miraculixx2014-12-08 21:01:22 +00:00Commented Dec 8, 2014 at 21:01
-
related (possibly a duplicate): Why don't computers come with specialized hardware such as sorting networks?gnat– gnat2014-12-08 21:01:29 +00:00Commented Dec 8, 2014 at 21:01
-
It already exists and it is already implemented in various forms in common desktop processors. String operations have been commonplace on computers since nearly day 1, and many architectures have had many different instructions catering to particular string handling schemes.whatsisname– whatsisname2014-12-08 21:50:15 +00:00Commented Dec 8, 2014 at 21:50
-
3Just buy an IBM mainframe -- had nearly all of these string operations as basic instructions since 1966.James Anderson– James Anderson2014-12-09 09:46:33 +00:00Commented Dec 9, 2014 at 9:46
|
Show 2 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you