In the context of an application monitoring numerous stock prices, how should the Pub/Sub subscription be configured to manage a high volume of messages and update the current stock price in a single large in-memory database, considering each message includes the stock symbol, price, and timestamp?