The (Hidden?) Costs of Vertex AI Resource Pools: A Cautionary Tale
Related
More from P. Galeone's blog
In recent months, I embarked on a journey to transform the UI/UX of a side project—bot.eofferte.eu, a SaaS platform that automates Amazon affiliate marketing on Telegram and streamlines the Amazon Associates onboarding process. The project’s architecture is straightforward: a Go backend powered by the labstack/echo framework, with UI rendering...
Starting from Unreal Engine 5.3, Epic Games added support for the so-called modern Xcode workflow. This workflow allows the Unreal Build Tool (UBT) to be more consistent with the standard Xcode app projects, and to be compliant with the Apple requirements for distributing applications… In theory! 😅 In practice this workflow is flawed: both the...
Large Language Models (LLMs) are well-suited for working with non-structured data. So far, their usage with structured data hasn’t been explored in depth although structured data is everywhere relational databases are. Making an LLM able to interact with a relational database can be an interesting idea since it will unlock the possibility of...
Gemini - the multimodal large language model developed by Google - is already available on Vertex AI for production-grade applications. As with any other Vertex AI product, it is possible to interact with it using clients built in different languages such as Python, Java, and Go or using plain HTTP requests. After all, Vertex AI is just a web...
This article shows a different approach to solving the same problem presented in the article AutoML pipeline for tabular data on VertexAI in Go. This time, instead of relying on AutoML we will define the model and the training job ourselves. This is a more advanced usage that allows the experienced machine learning practitioner to have full...