> For the complete documentation index, see [llms.txt](https://george-jen.gitbook.io/data-science-and-apache-spark/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://george-jen.gitbook.io/data-science-and-apache-spark/computer_needed.md).

# Computer needed for this course

You need 2 computers. One for development and one for production.

If you do not have 2nd computer for Linux machine, there is Ubuntu 16.04 Virtual box image available for you to download, if there are plenty of CPU cores and memory capacity in your computer.

For my environment, there are 32GB RAM on my windows 10 laptop as a development Apache Spark workstation, and the Linux computer has Intel 8700 6 cores/12 thread CPU and 64GB RAM to run Apache Hadoop, Hive and Spark cluster that has 1 master and worker nodes running with docker, sufficient to simulate production Spark cluster environment whether on premise or in the cloud.

We will be writing the Spark Application in both Scala and Python

The codes that I developed for this class are in my GitHub site and you will be writing the same level of codes at the end of the course:

<https://github.com/geyungjen/jentekllc/tree/master/Spark>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://george-jen.gitbook.io/data-science-and-apache-spark/computer_needed.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.