angular2 mock test ii
0 码力 | 4 页 | 84.49 KB | 1 年前3Ubuntu 桌面培训 2010
. . . . . . . . . . . . . . . . . . . . . . . 1 I.II 自由软件运动、开源和 Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 I.II.I 自由软件运动 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 I.II.II 开源运动与 Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 I.III 关于 Ubuntu . . . . . . . . . . . . . . . . . . . . . Ubuntu 承诺 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 I.III.II Ubuntu 版本 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 I.III0 码力 | 540 页 | 26.26 MB | 1 年前3The DevOps Handbook
as possible i. Institutionalize rituals to increase safety, continuous improvement, and learning ii. Create mechanism to rapidly spread learning throughout the organization 2. Ch. 19 – Enable and Inject the effect by making the solutions available throughout the organization.” They are self-healing ii. Netflix – April 21, 2011; entire Amazon AWS US-EAST availability zone went down; Netflix was unaffected 3. Create bureaucracy rather than carefulness 4. Cultivate secrecy, evasion, and self-protection ii. Dr. Sidney Dekkar – Bad Apple Theory – you cannot eliminate error by eliminating the people who caused0 码力 | 9 页 | 25.13 KB | 5 月前3The DevOps Handbook
flow of work by implementing continuous delivery i. Create the foundation of our deployment pipeline ii. Enabling fast & reliable automated testing iii. Enabling & practicing continuous integration & testing releases representing the first time we see how an application behaves in a production-like environment ii. Don’t just document the environment specifications 1. Create a common build mechanism to create it SYSTEM i. ALL parts (code & environments) of the system are shared in a version control repository ii. Version control is for everyone in the value stream iii. Everything, everything, everything is checked0 码力 | 8 页 | 23.08 KB | 5 月前3The DevOps Handbook
1. Introduction a. Goal – Implement fast feedback loops i. Enable working towards shared goals ii. See problems as they occur iii. Enable quick detection & recovery iv. Ensure features operate as to solving problems using telemetry to understand contributing factors and focus problem-solving. ii. Telemetry – An automated communications process by which measurements and other data are collected don’t just log what’s interesting to development. Operations don’t just monitor what’s up or down. ii. Modern Monitoring architecture 1. Data Collection at business logic, application, & environments0 码力 | 8 页 | 24.02 KB | 5 月前3The DevOps Handbook
customer b. THE BUSINESS VALUE OF DEVOPS i. Code and change deployments (thirty times more frequent) ii. Code and change deployment lead time (two hundred times faster) iii. Production deployments (sixty making it visible, all stakeholders can more easily prioritize work in the context of global goals. ii. REDUCE BATCH SIZES1. Another key component to creating smooth and fast flow is performing work in actively suppressing, even punishing, learning and improvement, perpetuating quality and safety problems ii. high-trust culture 1. we are all lifelong learners who must take risks in our daily work 2. we learn0 码力 | 8 页 | 22.57 KB | 5 月前3Laravel 5.0 Documentation
Introduction 2. Prologue i. Release Notes i. Laravel 5.0 ii. Laravel 4.2 iii. Laravel 4.1 ii. Upgrade Guide i. Upgrading To 5.0 From 4.2 ii. Upgrading To 4.2 From 4.1 iii. Upgrading To 4.1.29 From Contribution Guide i. Bug Reports ii. Core Development Discussion iii. Which Branch? iv. Security Vulnerabilities v. Coding Style 3. Setup i. Installation i. Install Composer ii. Install Laravel iii. Server Server Requirements ii. Configuration i. Introduction ii. After Installation iii. Accessing Configuration Values iv. Environment Configuration v. Configuration Caching vi. Maintenance Mode vii.0 码力 | 242 页 | 1.44 MB | 1 年前3What's New In Apache Ozone 1.3
Ozone 1.3 陈怡 Apache Ozone PMC 主席 3 ⽬录 I. Ozone 构架 II. Ozone 1.3 新功能 III. 未来展望 4 Ozone 构架 5 Ozone 1.3 新功能 I. 纠删码(Erasure coding) II. 系统均衡器(Container Balancer) III. 性能优化 - ⽂件系统优化(File System RS(3,2) 2 60% 以计算为代价,满⾜数据可靠性的同时, 降低数据存储成本 数据可靠性 vs. 存储效率 7 Ozone条带纠删码 I. 物理块:每个DN磁盘上的数据块,默认256MB II. 逻辑EC块:满⾜EC策略的⼀个⽤户数据块。例如RS-3-2,⼀个逻辑块3*256MB⼤⼩ III. 条带:条带的默认粒度1MB,可配置 IV. EC Container Group:给定Co 内建⽀持的策略 I. RS-3-2-1024K II. RS-6-3-1024K III.XOR-2-1-1024K II. 可定制新的策略 III.策略设置⽀持 I. 全局策略设置 II. 桶级别策略设置 III.对象/⽂件级别策略设置 12 Container Balancer 时机 I. 新的节点加⼊Ozone集群 II. 删除⼤量数据后 好处 III.充分利⽤集群资源0 码力 | 24 页 | 2.41 MB | 1 年前3Exceptions Under the Spotlight
future. MOTIVATION 4• Part 0: Prologue: What are Exceptions? • Part I: History and Domain • Part II: Exceptions Overhead • Part III: Design Overview • Part IV: Alternatives • Part V: What’s Next? OUTLINE language-level concept. Exceptions are platform-independent. • C++ Exceptions followABI rules. 18PART II: EXCEPTIONS OVERHEAD 19• Main difference between C and C++ is that the cleanup process is now part stack unwinding PART II: EXCEPTIONS OVERHEAD • Terms: • “Happy path” is the default scenario with no exceptions or errors. • “Sad path” is the path which includes errors. 20PART II: EXCEPTIONS OVERHEAD0 码力 | 53 页 | 2.82 MB | 5 月前32.1.3 如何用Go模拟CPU
Go模拟6502 • 小结 • 冯诺伊曼架构 约等于 有限状态机 • 用Go实现全部合法指令并测试通过也就1000行左右 说了这么多CPU 那电脑咋工作的? Go模拟Apple II • Apple II 规格 • CPU (MOS 6502) • 内存(64KiB) • 显示(LoRes 40x24) • 显示(280×192像素) • 输入(内置键盘) • 存储(磁带/5.25英寸) 早期内存非常昂贵 • 4KiB = 5,543 USD (2020) • 64KiB = 11,266 USD (2020) • 这么看现在的厨子是不是超良心 Go模拟Apple II • 模拟Apple II 规格 • CPU (MOS 6502) • 内存(64KiB) • 显示(LoRes 40x24) • 输入(内置键盘) • 存储(磁带/5.25英寸) • 早期内存非常昂贵 • 这么看现在的厨子是不是超良心 • 真果粉应该搞一套Apple II Go模拟Apple II • 又双叒叕是一个大循环 • Reset -> 启动检查程序 • 检查完成把电脑规格写入内存指定区域 • 一直循环monitor 函数 • 直到有NMI/IRQ中断 • 还是不懂…… • 就来个键盘敲下,到显示的全流程? Go模拟Apple II 按下键盘 硬件触发IRQ 键值写入0xC0000 码力 | 42 页 | 7.10 MB | 1 年前3
共 1000 条
- 1
- 2
- 3
- 4
- 5
- 6
- 100