MarkSfik commented on a change in pull request #365:
URL: https://github.com/apache/flink-web/pull/365#discussion_r466275367



##########
File path: _posts/2020-08-03-external-resource.md
##########
@@ -0,0 +1,142 @@
+---
+layout: post
+title: "Accelerating your workload with GPU and other external resources"
+date: 2020-08-03T12:00:00.000Z
+authors:
+- yangze:
+  name: "Yangze Guo"
+categories: news
+excerpt: This post introduces the new External Resource Framework in Flink 
1.11 and take GPU as an example to show how to accelerate your workload with 
external resources.
+---
+
+Apache Flink 1.11 introduces a new [External Resource 
Framework](https://ci.apache.org/projects/flink/flink-docs-master/ops/external_resources.html),
+which allows you to request external resources from the underlying resource 
management systems (e.g., Kubernetes) and accelerate your workload with
+those resources. As Flink provides a first-party GPU plugin at the moment, we 
will take GPU as an example and show how it affects Flink applications
+in the AI field. Other external resources (e.g. RDMA and SSD) can also be 
supported [in a pluggable 
manner](https://ci.apache.org/projects/flink/flink-docs-master/ops/external_resources.html#implement-a-plugin-for-your-custom-resource-type).
+
+# End-to-end real-time AI with GPU
+
+Recently, AI and Machine Learning have gained additional popularity and have 
been widely used in various scenarios, such
+as personalized recommendation and image recognition. 
[Flink](https://flink.apache.org/), with the ability to support GPU

Review comment:
       ```suggestion
   as personalized recommendation and image recognition. 
[Flink](https://flink.apache.org/), with its ability to support GPU
   ```




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to