BB@C Lugano UK ldt Information

BB@C has 2 main tasks; on going implemented project disclosable upon NdA <(1)> A challenge in cloud resource management is to design self-adaptable solutions capable to react to unpredictable workload fluctuations and changing utility principles analyzed from the perspective of an ASP that uses a cloud infrastructure to achieve scalable provisioning of its services in the respect of QoS constraints First was taxonomy of IaaS provider usage of the identified features to drive the design of four/five autonomic service management architectures differing on the degree of control an ASP have on the system Implemented two/tree of this solutions and related mechanism to test at least 3 max 5 different resource provisioning policies The implemented testbed has been evaluated under a realistic workload based on Wikipedia access traces on Amazon EC2 platform The experimental evaluation performed confirms the proposed policies are capable to properly dimension the system resources making the whole system self-adaptable respect to the workload fluctuation Moreover having full control over the resource management plan allow to save up to the 32,7% of resource allocation cost always in the respect of SLA constraints <(2)> By improving the consortium blockchain’s performance for financial business applications the first surveyed typical records of transaction rates for various financial systems and the performance capacity of several known consortium blockchains at this moment in time The blockchain itself does offer few performance advantage but rather sacrifices performance to achieve tamper resistance The average transaction rates for blockchain technologies continuously improving have already reached over 2,000 TPS equivalent to the transaction rate for the Zengin System the common name for Japanese Banks’ Payment Clearing Network Next the reserchers analysed and improved the transaction rate for Hyperledger a Linux Foundation Project & Fabric (BB@C§'s) one of the open source software tools for implementing consortium blockchain The inventors found that inefficient message transfer between the platform container and the application container was the main cause of BB@C§ performance bottleneck Introduced efficient application programming interface (API) between the containers and improved the transaction rate from 725 to over 1,350 TPS over 86,8% increase Finally the reasercer & inventors analysed BB@C§’s performance under artificial network latency Result is BB@C§ running over a wide area network required to replace its consensus algorithm to improve its transaction rate because other causes of performance deterioration plus consensus algorithm seems to become dominant ...