Scale Up和Scale Out的区别

最新推荐文章于 2022-03-16 19:30:23 发布
最新推荐文章于 2022-03-16 19:30:23 发布
阅读量1.4w 收藏 6
点赞数 2
分类专栏： 海量数据处理 文章标签： scale out scale up 数据中心 application 扩展
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/Hipercomer/article/details/38375171
版权

Scale Out是指Application可以在水平方向上扩展。一般对数据中心的应用而言，Scale out指的是当添加更多的机器时，应用仍然可以很好的利用这些机器的资源来提升自己的效率从而达到很好的扩展性。


Scale Up是指Application可以在垂直方向上扩展。一般对单台机器而言，Scale Up值得是当某个计算节点（机器）添加更多的CPU Cores，存储设备，使用更大的内存时，应用可以很充分的利用这些资源来提升自己的效率从而达到很好的扩展性。

下木
关注
  • 2
    点赞
  • 踩
  • 6
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
Large Scale Machine Learning with Spark
02-28
Data processing, implementing related algorithms, tuning, scaling up and finally deploying are some crucial steps in the process of optimising any application. Spark is capable of handling large-scale batch and streaming data to figure out when to cache data in memory and processing them up to 100 times faster than Hadoop-based MapReduce.This means predictive analytics can be applied to streaming and batch to develop complete machine learning (ML) applications a lot quicker, making Spark an ideal candidate for large data-intensive applications. This book focuses on design engineering and scalable solutions using ML with Spark. First, you will learn how to install Spark with all new features from the latest Spark 2.0 release. Moving on, you’ll explore important concepts such as advanced feature engineering with RDD and Datasets. After studying developing and deploying applications, you will see how to use external libraries with Spark.
什么是Scale Up（纵向扩展）和Scale Out（横向扩展）？
JavaEdge全是干货的技术号
09-22 7616
1 Scale Out 即Scale horizontally，横向扩展，向外扩展 。 称为集群系统。指由多个节点组成的SAP HANA系统，这种系统的扩展主要以水平扩展方式（指增加节点的方式）来进行。 比如：我们向原有的web、邮件系统添加一个新机器。 2 Scale Up 即Scale vertically）纵向扩展，向上扩展。 称为单节点系统，指系统中只包括一个有效节点（如果需要HA时，可以将两个单节点以System Replication形式构成单节点的HA架构）。这种架构的系统只具有垂直扩展能力，
BWFS Scale-out NAS介绍
01-21
蓝鲸SONG（BlueWhale Scale-out NAS Gateway）是中科蓝鲸公司推出的横向扩展NAS系统产品。它通过把高速的NAS网关与统一的SAN存储系统和BlueWhale File System(BWFS)集成起来，提供优异的性能和高伸缩性。NAS网关支持横向扩展（Scale-out）以提高对外统一协议访问的性能和文件访问能力；统一的SAN存储系统既支持横向扩展（Scale-out）提高存储IO性能，又支持纵向扩展（Scale-up）提高存储容量；二者通过BWFS提供存储虚拟化和统一的命名空间。因此，SONG可以提供高性能、可扩展的文件共享服务，并支持多机多工作流或集群环境下的各种应用。
large scale machine learning with spark
05-09
Key Features, Get the most up-to-date book on the market that focuses on design, engineering, and scalable solutions in machine learning with Spark 2We use Spark's machine learning library in a big data environmentYou will learn to develop high-value applications at scale with ease and a personalized design, Book Description, Scaling out and deploying algorithms, interactions, and clustering are crucial steps in the process of optimizing any application. By maintaining and streaming data, Spark can figure out when to cache data in-memory, 100x faster than Hadoop and Mahoot. This means data streaming and analytics can run and complete jobs a lot quicker, making Spark ideal for large data-intensive applications., This book focuses on design, engineering, and scalable solutions in machine learning with Spark. You will learn how to install Spark with all new features as in the latest version Spark 2. You will also get to grips with Spark MLlib and Spark ML and its implementation for machine learning algorithms. Moving ahead, we'll explore about important concepts such as Dataframes and advanced feature engineering. After studying more about the development and deployment of an application, you will also find out about the other external libraries available for your data analysis., What you will learn, Solid theoretical understanding about machine learning algorithms and techniques for new and unknown datasetsSet up and configure Spark, and develop your first Spark application using Scala, Java, and SparkRUse ML and MLlib implement practical and large-scale machine learning pipelines and applications including collaborative filtering, classification, regression, clustering, association rule mining, twitter sentiment analysis, and dimensionality reductionScale up your machine learning application on large cluster or even cloud computing environment like Amazon EC2Enhance performance of your machine learning modelsTune your machine learning models for cross-validation, grid searching, hyperparameter tuning and train validation splitDeal with large-scale text data, including feature extraction and using text data as input to machine learning modelsDevelop machine learning application real-time streaming data using Spark Streaming
Large-Scale Software Architecture.pdf
09-25
Contents Preface xi Acknowledgments xvii 1 Introduction 1 1.1 What is Software Architecture 1 1.1.1 What software architecture is not 4 1.1.2 Attributes of software architecture 5 1.1.3 Definitions of other key architecture-related terms 7 1.1.4 Other types of architectures 8 1.2 Why Architect? 10 1.3 Architectural Viewpoint Summary 12 1.4 Other Software Architecture Approaches 16 1.4.1 The 4+1 Views 16 1.4.2 RM-ODP viewpoints 17 1.4.3 Bass architectural structures 1.4.4 Hofmeister software architecture views 1.5 Recommended Reading 2 RolesoftheSoftwareArchitect 21 2.1 Relationship to other key roles in development organization 25 Role: project management 25 Role: development team managers 25 Role: system architect/chief engineer 26 Role: chief software engineer 26 Role: hardware architect 27 Role: network architect 27 19 19 19 Role: technical leads of each release 28 Role: data architect 28 Role: systems engineering leads 28 Role: software systems engineering lead 29 2.2 Skills and Background for the Architect 29 2.3 Injecting Architecture Experience 31 2.4 Structuring the Architecture Team 32 2.5 Traps and Pitfalls Associated with the Role of Software Architect 33 2.5.1 Clear definition of leadership 34 2.5.2 Reporting structure for the software architect 34 2.5.3 Geographical location of software architect and technical leads 35 2.5.4 Architecture team size and composition 36 2.5.5 Software architect lifecycle participation 36 2.6 Recommended Reading 37 3 SoftwareArchitectureandtheDevelopment Process 39 3.1 Overview of Iterative Development 39 3.1.1 Overall process phases 40 3.1.2 Lifecycle stages 41 3.1.3 Architecture and agile processes 43 3.1.4 Start early, refine constantly 47 3.2 Requirements Management 48 3.2.1 Use cases and requirements engineering 48 3.2.2 Additional requirements that impact architecture 49 3.2.3 Requirements tracing 49 3.3 Management of the Technology Roadmap 50 3.3.1 External software products 50 3.3.2 Software technology management traps and pitfalls 53 3.3.3 Organizational technology roadmap 54 3.4 Effective Technical Meetings 55 3.4.1 Informal technical meetings 55 3.4.2 Peer reviews and inspections 56 3.4.3 Design reviews 57 3.4.4 Design communication meetings 57 3.4.5 Management meetings 57 3.4.6 Vendor presentations 58 3.4.7 Distributed technical meetings 58 3.5 Traps and Pitfalls of the Software Architecture Process Activities 59 The out-of-touch architect 59 Analysis paralysis 60 Design for reuse 60 Use cases 60 Schedule 60 3.6 Computer-Aided Software Engineering (CASE) Tools 61 3.7 Recommended Reading 62 vi Contents 4 ExampleSystemOverview 63 4.1 System Overview 64 4.2 Overview of System Interfaces 64 4.3 Constraints 67 4.4 Major Operational Requirements and Software Requirements 67 5 UMLQuickTour 69 5.1 UML Diagram Summary 69 5.2 General Diagramming Conventions 72 5.2.1 General UML features: stereotypes, tagged values, multi-instance 73 5.2.2 View labels 74 5.3 The Diagrams 75 5.3.1 Component instance diagrams 75 5.3.2 Class and subsystem diagrams 76 5.3.3 Interaction (sequence and collaboration) diagrams 77 5.3.4 Deployment diagrams 79 5.3.5 Statechart diagrams 80 5.3.6 Activity diagrams 81 5.4 Managing Complexity 81 5.4.1 Use Case focused modeling 82 5.4.2 Element focused modeling 82 5.4.3 Level of detail 83 5.4.4 Controlling the number of models 83 5.4.5 Use Supplemental Textural Information 85 5.5 Recommended Reading 85 6 SystemContext andDomainAnalysis 87 6.1 Conceptual Diagrams 87 6.2 Context Viewpoint 89 6.3 Domain Analysis Techniques 94 6.3.1 A formal analysis technique 95 6.3.2 Other techniques for finding domain entities 98 6.3.3 Analysis shortcuts 100 6.4 Analysis Viewpoints 101 6.4.1 Analysis Interaction Viewpoint 101 6.4.2 Analysis Focused Viewpoint 103 6.4.3 Analysis Overall Viewpoint 105 6.4.4 Candidate subsystem identification 107 6.5 Recommended Reading 108 7 Component DesignandModeling 111 7.1 Overview 111 7.1.1 Component-based development 111 7.1.2 Terminology 112 7.1.3 Communication and interfaces 115 7.1.4 Finding components 115 7.1.5 Qualities of component design 116 Contents vii 7.2 Component Viewpoint 116 7.2.1 Component communication 117 7.2.2 Component interfaces 118 7.2.3 Message-based component modeling 121 7.2.4 Combining interfaces and messaging 124 7.2.5 Comparison of interfaces and messaging 127 7.2.6 Mechanism and performance annotations 128 7.3 Component Interaction Viewpoint 131 7.3.1 Component to Component Interactions 131 7.4 Component State Modeling 133 7.5 Modeling Highly Configurable Component Architectures 137 7.6 Recommended Reading 137 8 SubsystemDesign 139 8.1 Terminology 139 8.2 Modeling Subsystems, Interfaces, and Layers 141 8.2.1 Subsystem Interface Dependency Viewpoint 141 8.2.2 Enhancing the Subsystem Dependency Views with layers 8.2.3 Top-level Dependencies 144 8.2.4 The Layered Subsystem Viewpoint 146 8.3 Mapping Subsystems and Layers to Implementation 151 8.3.1 Subsystems, layers, and build trees 151 8.3.2 Subsystems and components 8.4 Recommended Reading 154 9 TransactionandDataDesign 155 9.1 Logical Data Architecture 155 9.1.1 Logical data model stability 157 9.1.2 Effects of the stable logical data model 158 9.2 Logical Data Viewpoint 159 9.2.1 Logical Data View example 160 9.2.2 Logical Data View for messaging 9.3 Data Model Design – Other Considerations 9.3.1 Data models and layers 164 9.3.2 Data models and reflection 165 9.3.3 Mapping objects to relational database 166 9.4 Transaction Design 169 9.4.1 Transaction concepts 170 9.4.2 Modeling transaction dynamics 171 9.4.3 Transactions and interface design 173 9.5 Recommended Reading 174 10ProcessandDeployment Design 177 10.1 Physical Data Viewpoint 178 10.1.1 Modeling other storage attributes 179 10.1.2 Detailed physical storage modeling 181 10.2 Process Viewpoint 183 viii Contents 16 153 3 16 143 3 TEAMFLY Team-Fly ? 10.2.1 Processes and components 186 10.2.2 Process and component management 186 10.2.3 Process State Viewpoint 189 10.3 Deployment Viewpoint 193 10.3.1 Scalable node design 194 10.3.2 Backup/archive design 199 10.4 Recommended Reading 199 11ArchitectureTechniques 201 11.1 Architecture Development Techniques 201 11.1.1 Commonality and variability analysis 202 11.1.2 Design for change 203 11.1.3 Generative programming techniques 204 11.1.4 Building a skeleton system 205 11.1.5 Prototyping 206 11.1.6 Interface development – Design by Contract 206 11.1.7 Architectural description languages 208 11.1.8 Architecture evaluation 208 11.2 Software Partitioning Strategies – Separation of Concerns 208 11.2.1 Functional decomposition 209 11.2.2 Isolate donfiguration data 210 11.2.3 Isolate hardware-specific components 210 11.2.4 Isolate time-critical components 211 11.2.5 Separate domain implementation model from human interface 211 11.2.6 Separate domain implementation model from implementation technology 211 11.2.7 Separate main function from monitoring 212 11.2.8 Separate fault recovery processing 212 11.2.9 Adaptation of external interfaces 213 11.3 Software Changeability and Dependency Management 213 11.3.1 The stable dependencies principle (SDP) 214 11.3.2 Acyclic dependencies principle 215 11.3.3 Interface Separation Principle 216 11.4 Using Architectural Patterns 216 11.5 Integration Strategies 218 11.5.1 Data-only integration 219 11.5.2 Executable integration 220 11.6 Establishing Architecture to Support Development 221 11.6.1 Configuration and change management 221 11.6.2 Build management 222 11.6.3 Continuous integration 222 11.6.4 Anticipate multi-language development 223 11.6.5 Anticipate tactical development (scripting) 224 11.7 Recommended Reading 225 12ApplyingtheViewpoints 227 12.1 Bottom-Up Architecture Development 227 12.2 Top-Down Architecture Development 229 Contents ix 12.3 Message Protocol and Interface Development 231 12.4 Reengineering Existing Systems 233 12.5 Documenting the Architecture 233 12.6 Conclusions 235 12.6.1 Becoming an architect 235 12.6.2 State of the Practice 237 12.6.3 Looking forward 238 12.6.4 Final thoughts 240 12.7 Recommended Reading 241 Appendix:SummaryofArchitectural Viewpoints 243 Bibliography 251 Index 257
scale out和scale up的区别
zy103118的博客
04-25 4651
理解Scale Out和Scale Up
u010819622的博客
11-19 1541
Scale Out是指Application可以在水平方向上扩展。一般对数据中心的应用而言，Scale out指的是当添加更多的机器时，应用仍然可以很好的利用这些机器的资源来提升自己的效率从而达到很好的扩展性。 Scale Up是指Application可以在垂直方向上扩展。一般对单台机器而言，Scale Up值得是当某个计算节点（机器）添加更多的CPU Cores，存储设备，使用更大的内存时，...
转mysql横向扩展和纵向扩展
weixin_30367543的博客
08-06 152
Scale-up（纵向扩展）和Scale-out（横向扩展）的解释 　　谈到系统的可伸缩性，Scale-up（纵向扩展）和Scale-out（横向扩展）是两个常见的术语，对于初学者来说，很容易搞迷糊这两个概念，这里总结了一些把概念解释的比较清楚的内容。 　　首先来段Wikipedia的，讲的很透彻了。 Scale vertically (scale up) 　 　To scale vert...
scale-out与scale-up的区别
weixin_30507269的博客
07-16 536
Scale Out（也就是Scale horizontally）横向扩展，向外扩展 Scale Up（也就是Scale vertically）纵向扩展，向上扩展 无论是Scale Out，Scale Up，Scale In，实际上就是一种架构的概念，这些概念用在存储上可以，用在数据库上，网络上一样可以 简单地说，scale-out，scale-up都是扩展。为什么需要扩展？随着数据量...
Scale Up和Scale Out
zhigangsun的专栏
06-09 1032
Scale Out（也就是Scale horizontally）横向扩展，向外扩展 Scale Up（也就是Scale vertically）纵向扩展，向上扩展 无论是Scale Out，Scale Up，Scale In，实际上就是一种架构的概念，这些概念用在存储上可以，用在数据库上，网络上一样可以。 简单比喻下Scale out和Scale up，帮助我们理解： Scale Out，比
云计算在电信业上面临的挑战和机遇
01-19
　区别于大小型机等为代表的单机超强计算能力的思想（Scale Up模式），云计算基本的概念是以性价比的X86 服务器硬件为基础，利用服务器虚拟化、网络虚拟化、分布式计算、并行处理、集群调度管理、Web 2.0等软件技术...
Scale up 与 Scale out
czhf0002的博客
12-02 195
​新时代的少先队员镇个楼查下scale的意思。scale英[skeɪl]美[skeɪl]n.规模; (尤指与其他事物相比较时的)范围; 程度; 等级; 级别; 等级体系;vt.攀登; 到达...
系统扩展方式 scale up和scale out
热门推荐
Truong的专栏
06-11 2万+
什么是scale up和scale out? 　　许多存储系统开始很简单，但当需要进行系统扩展时就会变得复杂。升级存储系统最常见的原因是需要更多的容量，以支持更多的用户，文件，应用程序或连接的服务器。 　　但是通常，存储系统的升级不只是需要容量，系统还对其他存储资源有额外需求，即带宽和计算能力。如果没有足够的I/O带宽，将出现用户或服务器的访问瓶颈;没有足够的计算能力，常用的存储软件如
HANA的可扩展性
In-Memory Computing Technology
06-02 7830
可扩展性HANA支持Scale-Up和Scale-Out。Scale-Up(纵向扩展)是指在计算单元内增加资源。而Scale-Out(横向扩展)是指添加其它的计算单元，并逻辑上形成一个整体。纵向扩展(Scale-Up)最常见的纵向扩展方式就是添加CPU（内存也相应添加了），也即NUMA架构。由于每个socket都有自己的内存控制器，访问本地和远程的内存性能是不一样的额，因此称为Non-Uniform
昆仑分布式数据库之ScaleOut介绍
KunLunDB_Linda的博客
03-09 904
一、分布式数据库的基础核心能力-水平扩容（ScaleOut） 数据库系统架构的演变，如实的反映了信息社会不断发展所带来的数据处理规模不断变大这一基本事实。 如今，分布式数据库产品已成为各行各业信息系统的存储服务中，应用越来越广泛的技术选型。究其原因，是因为其在海量数据存储管理的扩展能力和性价比方面，较单机数据库有着压倒性的优势。 在我们对昆仑分布式数据库的扩容功能正式开始介绍之前，我们首先回顾一下数据库管理系统扩容的常见模式。 数据库的扩容大体上分为如下两种模式：垂直扩容（Vertically Sc
什么是横向扩展和纵向扩展？
后场技术
03-16 7740
现代应用程序不断变化，随着新要求的发展而发展，并且存在于对资源的不同需求的环境中。扩展应用程序可以根据资源需求适当调整其大小，以确保客户满意并降低基础设施成本。如果您不知道如何有效地扩展，...
云存储的未来：Scale Up还是Scale Out？
omnigeeker的博客
12-05 3317
云存储的几十年发展历程，其计算架构模型，也从Scale Up走向Scale Out。但是展望未来数字世界的海量需求，目前流行的模型还能够持续满足吗？本文通过对云存储历史的回顾，及对Scale Up和Scale Out两种扩展模型的诠释，来揭开云存储的未来模式。 1. 云存储及其历史 简而言之，云存储（cloud storage）就是将数字内容安全的存储在服务器上，从而任何连接互联网的设备可以方便...
什么是横向扩展、纵向扩展？
逍遥壮士
12-13 8582
什么是横向扩展、纵向扩展？ 横向扩展英文简称：Scale Out，全称：Scale horizontally，横向扩展，向外扩展。 纵向扩展英文简称：Scale Up，全称：Scale vertically，纵向扩展，向上扩展。 不管横向扩展还是纵向扩展都是一种架构的概念。 横向扩展：比如可以增加一台节点/机器 比如：mysql新增加一个从库、tomcat新增加一台机器; 纵向扩展：比如可以通过修改mysql参数内存比例、修改tomcat的线程数; 注：如果纵向扩展升级硬件比如CPU升级成6..
存储scale-up和scalce-out架构
ganggexiongqi的专栏
09-05 3173
存储scale-up和scalce-out架构 Scale-up，即纵向扩展架构。从下面的拓扑图我们可见，纵向扩展是利用现有的存储系统，通过不断增加存储容量来满足数据增长的需求。HDS Scale-out横向扩展架构的升级通常是以节点为单位，容量和性能会同步增长。有几种方法可以实现scale-out，即横向扩展，包括集群存储系统和网格存储。但无论是哪种类型的系统，能够以一个单一系统的形
Scale-Up和Scale-Out有什么区别？
最新发布
05-05
Scale-Up和Scale-Out是两种不同的扩展计算资源的方式。 Scale-Up指的是垂直扩展，即增加单个计算节点的处理能力，例如增加CPU核心、内存、存储等硬件资源。这种扩展方式通常需要更高的成本，并且通常有一个物理限制...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值