# OpenShift Published articles for OpenShift. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Keycloak Performance Benchmarks: A Deep Dive into Scaling and Sizing (26.4) DevFeed: [Keycloak Performance Benchmarks: A Deep Dive into Scaling and Sizing (26.4)]() Original publisher: [Read original article]() Author: Pedro Ruivo Published: 2025-10-01T00:00:00Z Content type: article Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [Benchmark](), [Availability](), [Databases](), [PostgreSQL](), [Amazon Web Services]() Tags: [amazon-aurora](), [availability](), [aws](), [benchmarks](), [idm](), [kerberos](), [keycloak](), [ldap](), [openid-connect](), [openshift](), [performance](), [postgresql](), [saml](), [sso]() ### AI overview This article presents Keycloak 26.4 benchmark results covering scaling under increasing login and refresh-token load, resource sizing, high availability, artificial network latency, and caching for database usage. In the tested range, Keycloak scaled almost linearly when scaled vertically. ### Source excerpt When deploying a mission-critical component like Keycloak, performance is a top concern. Questions about resource requirements, high availability, and network latency are crucial for a successful and stable production environment. To provide a clear, data-driven perspective on these topics, we conducted a series of benchmarks on the latest Keycloak version 26.4. In this post, we'll share our findings on how Keycloak scales with increasing load, performs under artificial network latency, and leverages caching to optimize database usage. Share your feedback about this blog post in our forum! Environment OpenShift 4.17 deployed across three availability zones in eu-west-1. Provisioned using Red Hat OpenShift Service on AWS (ROSA), with ROSA HCP. At least one worker node in each availability zone. Amazon Aurora PostgreSQL 17.5 database. Configured for high availability, with a primary DB instance in one availability zone and synchronously replicated readers in the other availability zones. Database populated with 100,000 users. Keycloak Benchmark as the load generator. The benchmark ran on 20 to 50 t4g.small AWS instances in the same region. Scaling Keycloak One of the most common questions when deploying Keycloak is: how many resources do I need? The answer, as you may have guessed, is that it depends on your specific use case. For this test, we scaled only the login and refresh token requests. Based on Keycloak's Concepts for sizing CPU and memory resources documentation, we determined that you need 1 vCPU to handle 15 logins per second and an additional 1 vCPU to handle 120 refresh token requests per second. After computing the total number of vCPUs required, we divided the value by the desired number of Pods, which was three in this case (one for each availability zone). We allocated slightly more vCPU to each Pod than the calculated value to account for JVM background tasks like compilations and garbage collection. Because our test used a constant load, we did not ## Keycloak on OpenShift DevFeed: [Keycloak on OpenShift]() Original publisher: [Read original article]() Author: Stian Thorgersen Published: 2018-05-31T00:00:00Z Content type: tutorial Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [Node.js](), [HTML5]() Tags: [deployment](), [how-to](), [html5](), [idm](), [kerberos](), [keycloak](), [ldap](), [node-js](), [openid-connect](), [openshift](), [saml](), [sso]() ### AI overview A tutorial showing how to deploy Keycloak on OpenShift, then deploy a Node.js REST service and an HTML5 application and secure both with Keycloak. ### Source excerpt In this post you'll see how to deploy Keycloak on OpenShift. You'll also learn how to deploy a Node.js based REST service and an HTML5 application to OpenShift and secure these with Keycloak. There is also a screencast showing this example at https://youtu.be/9zUWqbK3BqI. If you don't already have OpenShift available a good place to start is by using MiniShift. Deploying Keycloak First of all create a new project in OpenShift with oc by running: oc new-project keycloak The next thing to do is to import the Keycloak template into OpenShift, by running: oc replace --force -f "https://raw.githubusercontent.com/jboss-dockerfiles/keycloak"\ "/master/openshift-examples/keycloak-https.json" Now open the OpenShift console and open the keycloak project. Click on Add to Project and Browse Catalog. In the catalog you should find Keycloak. Click on it. Click next on the information. Under configuration set a username and password that you can remember in the Keycloak Administrator Username and Keycloak Administrator Password fields. Then click on create. Click on Continue to project overview. Wait for the deployment to complete then click on the link to the application. Your browser will complain about the certificate as it is a self-signed certificate. Ignore this and proceed. Click on Administration Console, then login with the username and password you entered previously. Keep this tab open as you will need it later. You have now deployed Keycloak onto OpenShift. Configure Clients in Keycloak We need to create clients for the service and the application we will secure. Open the tab with the Keycloak admin console. Click on Clients and Create. For Client ID enter service and click Save. Under Access Type select bearer-only and click on Save. Click on Clients then Create again. For Client ID enter app and click Save. For Valid Redirect URIs and Web Origins enter *. In production environment it is very important that you enter the correct URL for your application, but since thi