Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Enhancing Data Syncing Using Kubernetes (K8s) #4065

Closed
H0llyW00dzZ opened this issue Feb 19, 2024 · 2 comments
Closed

[Feature] Enhancing Data Syncing Using Kubernetes (K8s) #4065

H0llyW00dzZ opened this issue Feb 19, 2024 · 2 comments

Comments

@H0llyW00dzZ
Copy link
Contributor

Describe the solution you'd like
A potential improvement could be to implement data syncing using Kubernetes (K8s), as an alternative to webdav and others. This would leverage the robustness and scalability of Kubernetes, making the data syncing process more efficient.

Describe alternatives you've considered
Kubernetes provides an economical means for data syncing. By using a RESTful API, chat history could be synced and stored within the cluster. This approach could replace the current system, possibly resulting in cost savings and improved performance.

Note

Utilizing Kubernetes for data syncing is a cost-effective solution. Kubernetes' inherent capabilities for load balancing, service discovery, and seamless scaling could significantly enhance the efficiency and reliability of data syncing.

Additional context
This suggestion stems from the need to optimize data syncing processes. It is anticipated that implementing such a solution could lead to improved system performance, reduced costs, and better data management within the cluster. Any additional insights or suggestions related to this proposal would be greatly appreciated.

@H0llyW00dzZ
Copy link
Contributor Author

Example how it cost-effective solution, with better configuration

$ kubectl top nodes
NAME                   CPU(cores)   CPU%   MEMORY(bytes)   MEMORY%   
pool-zcvjeogy9l-fpf0k   70m          3%     1914Mi          61%
pool-p2heexrowh-q48el   50m          2%     1423Mi          45%
pool-uzgnmaho58-qtd3u   46m          2%     1643Mi          52%
pool-1gcdtzmc93-8d3k2   29m          1%     939Mi           30%
pool-5dmiurdb5l-i68gt   32m          1%     1693Mi          54%
pool-zxu274nveu-alavv   34m          1%     866Mi           27%

@H0llyW00dzZ
Copy link
Contributor Author

Bump testing another

this repo running on k8s without crash

$ kubectl get pods
NAME                       	 READY    STATUS    RESTARTS   	   AGE
mysql-ptw2wl7guc-gfs8p      	  1/1     Running   	0          17h
chatgptnextweb-alqritdqd0-mz4yh   1/1     Running   	0          15h
chatgptnextweb-alqritdqd0-kfbn5   1/1     Running   	0          15h
chatgptnextweb-alqritdqd0-recw3   1/1     Running   	0          15h
$ kubectl top pods
NAME                       	CPU(cores)   MEMORY(bytes)   
mysql-ptw2wl7guc-gfs8p      	  5m           436Mi
chatgptnextweb-alqritdqd0-mz4yh   0m           49Mi
chatgptnextweb-alqritdqd0-kfbn5   0m           50Mi
chatgptnextweb-alqritdqd0-recw3   1m           54Mi

@ChatGPTNextWeb ChatGPTNextWeb locked and limited conversation to collaborators Feb 26, 2024
@fred-bf fred-bf converted this issue into discussion #4132 Feb 26, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant