The Logo Generator’s primary steps

For this application, we will use a logo finetuned LoRA with the Stable Diffusion XL model, which will indeed yield impressive results. Here are the primary steps for logo generation using this approach:

  1. Text Input: The user provides a text description(prompt) of the desired logo, such as “a logo for a coffee shop, coffee”, along with a negative prompt and colors.
  2. Model Processing: This text prompt is fed into the Stable Diffusion XL model, which processes the inputs and generates a corresponding logo representation.
  3. Logo Output: Finally, the model outputs a unique logo based on the given text description, capturing the desired visual elements and style.

Crafting Your Application

To build the logo generator application, we’ll be using these tools:

  • Diffusers: A library specifically designed for diffusion models, offering utilities for loading, processing, and generating images.
  • Inferless: A serverless platform that simplifies the deployment and scaling of machine learning models, allowing us to serve our logo generator application easily.

Core Development Steps

Text-to-Logo Generation

  • Objective: Accept user text input, generate a logo image using the Stable Diffusion XL model with LoRA, and return the generated logo.
  • Action: Implement a Python class (InferlessPythonModel) that handles the entire text-to-logo generation process, including input handling, model integration, and logo generation.
import json
import torch
from diffusers import DiffusionPipeline, DPMSolverMultistepScheduler
import base64
from io import BytesIO


class InferlessPythonModel:
    """
    Class for text-to-image generation using Stable Diffusion with LoRA
    """

    def initialize(self):
        """
        Initializes the model, scheduler, and loads model weights.
        """
        model_id = "stabilityai/stable-diffusion-xl-base-1.0"
        lora_id = "artificialguybr/LogoRedmond-LogoLoraForSDXL-V2"

        # Load the diffusion model with FP16 precision for efficiency
        self.pipe = DiffusionPipeline.from_pretrained(model_id, variant="fp16")

        # Use the high-performance DPMSolver++ scheduler for faster inference
        scheduler = DPMSolverMultistepScheduler(use_karras_sigmas=True, algorithm_type="sde-dpmsolver++")
        self.pipe.scheduler = scheduler.from_config(self.pipe.scheduler.config)

        # Load LoRA weights for text-based guidance
        self.pipe.load_lora_weights(lora_id)

        # Move model to GPU for faster processing
        self.pipe.to(device="cuda", dtype=torch.float16)

    def infer(self, inputs):
        """
        Generates an image based on the provided prompt.
        """
        prompt = inputs["prompt"]
        negative = inputs["negative_prompt"]
        color = inputs["color"]
        complete_prompt = f'logo, {prompt} colors ({color})'
  
        pipeline_output_image = self.pipe(
            prompt=complete_prompt,
            negative_prompt = negative,
            num_inference_steps=30,
            guidance_scale=7,
        ).images[0]

        # Encode the generated image as a base64 string for convenient transfer
        buff = BytesIO()
        pipeline_output_image.save(buff, format="PNG")
        img_str = base64.b64encode(buff.getvalue())
        return {"generated_image_base64": img_str.decode("utf-8")}

    def finalize(self, args):
        """
        Cleans up model resources to prevent memory leaks.
        """
        self.pipe = None

Setting up the Environment

Dependencies:

  • Objective: Ensure all necessary libraries are installed.
  • Action: Run the command below to install dependencies:
pip install accelerate==0.28.0 diffusers==0.27.0 transformers==4.38.2 peft==0.9.0

This command ensures your environment has all the tools required for the application.

Deploying Your Model with Inferless CLI

Inferless allows you to deploy your model using Inferless-CLI. Follow the steps to deploy using Inferless CLI.

Clone the repository of the model

Let’s begin by cloning the model repository:

git clone https://github.com/inferless/Logo-Generator.git

Deploy the Model

To deploy the model using Inferless CLI, execute the following command:

inferless deploy --gpu A100 --runtime inferless-runtime-config.yaml

Explanation of the Command:

  • --gpu A100: Specifies the GPU type for deployment. Available options include A10, A100, and T4.
  • --runtime inferless-runtime-config.yaml: Defines the runtime configuration file. If not specified, the default Inferless runtime is used.

Demo of the Logo Generator

Here are a few examples of logos generated from our application:

Alternative Deployment Method

Inferless also supports a user-friendly UI for model deployment, catering to users at all skill levels. Refer to Inferless’s documentation for guidance on UI-based deployment.

Choosing Inferless for Deployment

Deploying your Logo Generator app with Inferless offers compelling advantages, making your development journey smoother and more cost-effective. Here’s why Inferless is the go-to choice:

  1. Ease of Use: Forget the complexities of infrastructure management. With Inferless, you simply bring your model, and within minutes, you have a working endpoint. Deployment is hassle-free, without the need for in-depth knowledge of scaling or infrastructure maintenance.
  2. Cold-start Times: Inferless’s unique load balancing ensures faster cold-starts. Expect around 5.32 seconds to process each logo, significantly faster than many traditional platforms.
  3. Cost Efficiency: Inferless optimizes resource utilization, translating to lower operational costs. Here’s a simplified cost comparison:

Scenario 1

You are looking to deploy a Logo Generator application for processing 100 logos per day.

Parameters:

  • Total number of Logo: 100 daily.
  • Inference Time: All models are hypothetically deployed on A100 80GB, taking 5.32 seconds of processing time and a cold start overhead of 11.72 seconds.
  • Scale Down Timeout: Uniformly 60 seconds across all platforms, except Hugging Face, which requires a minimum of 15 minutes. This is assumed to happen 100 times a day.

Key Computations:

  1. Inference Duration:
    Processing 100 logos and each takes 5.32 seconds
    Total: 100 x 5.32 = 532 seconds (or approximately 0.15 hours)
  2. Idle Timeout Duration:
    Post-processing idle time before scaling down: (60 seconds - 5.32 seconds) x 100 = 5468 seconds (or 1.52 hours approximately)
  3. Cold Start Overhead:
    Total: 100 x 11.72 = 1172 seconds (or 0.33 hours approximately)

Total Billable Hours with Inferless: 0.15 (inference duration) + 1.52 (idle time) + 0.33 (cold start overhead) = 2 hours
Total Billable Hours with Inferless: 2 hours

Scenario 2

You are looking to deploy a Logo Generator application for processing 1000 logos per day.

Key Computations:

  1. Inference Duration:
    Processing 1000 logos and each takes 5.32 seconds Total: 1000 x 5.32 = 5320 seconds (or approximately 1.48 hours)‍
  2. Idle Timeout Duration:
    Post-processing idle time before scaling down: (60 seconds - 5.32 seconds) x 100 = 5468 seconds (or 1.52 hours approximately)
  3. Cold Start Overhead:
    Total: 100 x 11.72 = 1172 seconds (or 0.33 hours approximately)

Total Billable Hours with Inferless: 1.48 (inference duration) + 1.52 (idle time) + 0.33 (cold start overhead) = 3.33 hours
Total Billable Hours with Inferless: 3.33 hours

Scenario 3

You are looking to deploy a Logo Generator application for processing 10000 logos per day.

Key Computations:

  1. Inference Duration:
    Processing 10000 logos and each takes 5.32 seconds Total: 10,000 x 5.32 = 53,200 seconds (or approximately 14.78 hours)‍
  2. Idle Timeout Duration:
    Post-processing idle time before scaling down: (60 seconds - 5.32 seconds) x 100 = 5468 seconds (or 1.52 hours approximately)
  3. Cold Start Overhead:
    Total: 100 x 11.72 = 1172 seconds (or 0.33 hours approximately)

Total Billable Hours with Inferless: 14.78 (inference duration) + 1.52 (idle time) + 0.33 (cold start overhead) = 16.63 hours
Total Billable Hours with Inferless: 16.63 hours

Pricing Comparison for all the Scenario

ScenariosAWS SageMaker CostInferless Cost
100 requests/day$28.8 (24 hours billed at $1.22/hour)$2.44 (2 hours billed at $1.22/hour)
1000 requests/day$28.8 (24 hours billed at $1.22/hour)$4.06 (3.33 hours billed at $1.22/hour)
10000 requests/day$28.8 (24 hours billed at $1.22/hour)$20.29 (16.63 hours billed at $1.22/hour)

By opting for Inferless, you can achieve up to 91.52% cost savings.

Please note that we have utilized the A100(80 GB) GPU for model benchmarking purposes, while for pricing comparison, we referenced the A10G GPU price from both platforms. This is due to the unavailability of the A100 GPU in SageMaker.

Also, the above analysis is based on a smaller-scale scenario for demonstration purposes. Should the scale increase tenfold, traditional cloud services might require maintaining 2-4 GPUs constantly active to manage peak loads efficiently. In contrast, Inferless, with its dynamic scaling capabilities, adeptly adjusts to fluctuating demand without the need for continuously running hardware.

Conclusion

By following this guide, you’re now equipped to build and deploy a sophisticated logo generator application. This tutorial showcases the seamless integration of advanced technologies, emphasizing the practical application of logo generation for creating cost-effective solutions.